# Flow: from history to individual events

Investigate task execution with paginated history and details about stages, actors and model attempts.

Source: https://zild.ai/en-US/docs/apps/zild-tasks/updates-flow-historico-eventos

Investigate task execution with paginated history and details about stages, actors and model attempts.

## How to use it

In Zild Admin, open Flow activity under Compliance and filter the incident period. Select an event to inspect its task, stages, actor and description; the panel includes execution metadata when available. In Zild Flow, open the correct board and task to inspect its history. The Flow History list presents agent executions and should not be confused with task-event auditing.

## Limits and prerequisites

Tokens, provider, model and attempts depend on recorded event metadata. Missing fields should not be interpreted as zero usage. Viewing an event does not rerun the task or automatically fix a failure.

## Validate in your operation

Follow a test task across two stages and inspect the event sequence. When investigating failures, record task and event IDs to distinguish separate attempts.

## Verify the exported file

Use Excel to analyze results or the print option to prepare a printable view. The table exports columns configured for that purpose; action buttons and internal fields are not automatically included. Compare IDs, dates and a sample of events with the applied query.

If the total count changes while pages are being retrieved, or a page is missing, collection may fail and ask you to run the search again. Refresh the query and retry, preferably with a shorter period. A completed export is not an immutable database snapshot: to reproduce an analysis, also retain the period, filters and extraction time.

If printing does not open, check the message about the browser’s pop-up blocker. Wait for preparation to finish before closing the page.

## Filters, dates and export in Admin

In Admin flow auditing, select the period, flow, event types, agent and user, then use Refresh. To filter by user, select an autocomplete option: typing a name without selecting it does not apply a user ID. Clear removes filters and restores the initial 30-day period.

The calendar uses local days and includes the selected final day. The screen converts that interval to a query with an exclusive end. When comparing direct API calls or results with someone in another time zone, check dates and effective boundaries. Do not manually add a day to the calendar: the interface already makes that adjustment.

The table offers pages of 25, 50 or 100 events. Export retrieves all pages matching the applied filters, not only the visible page. After changing fields, use Refresh before exporting: unapplied edits do not change the exported query. Check the period and data before sharing. Filters are stored in the URL, but sharing the link does not grant access permission. Open a row to inspect the event details and task sequence.

## Audit query permission and time range

The paginated audit query requires ViewTenantConfig permission. Without it, a 403 response does not mean there are no events: request access from the responsible administrator.

The API time range uses UTC, includes the starting instant and excludes the ending instant. To query a full day, provide the start of that day and the start of the next day. The supplied interval must not exceed 366 days. Without a period, general searches cover the last 30 days; a single-task query does not receive this default period. Each page accepts up to 100 records.

A 400 response calls for checking the period, pagination or identifiers. Verify these parameters before concluding that a record is missing. These rules apply to the audit query, not the seven-day filter in the agent execution list.

## Choose the appropriate investigation view

Use task history for its event sequence and Admin auditing for recorded execution details. Before comparing indicators, check dashboard filters: a task can have human and AI participation, and task creation dates differ from execution dates.

[Investigate a task](/en-US/docs/apps/zild-tasks/task-history-id/) · [Query agent executions](/en-US/docs/apps/zild-tasks/task-history/) · [Interpret the dashboard](/en-US/docs/apps/zild-tasks/task-dashboard/)

## Availability

Feature identified in the platform code in October 2026. Availability depends on the deployed version, permissions and environment connectors. Contact Zild if it is not visible yet.

Documentation reviewed: 2026-10-28.

[Read the announcement](/en-US/blog/flow-historico-eventos)