Logs

What are Logs?

Logs give you a record of native Flow and Agent executions and external executions reported through the OpenTelemetry Protocol (OTLP). External executions sent to the JSON compatibility ingest endpoint, POST /v1/executions/ingest, appear in Runs and eval capture but do not produce structural Logs or trace records. A retained log entry can record when an execution started, which steps ran, what data moved between them, and whether the execution succeeded or failed. Logs also include workspace changes when your plan includes the audit trail. The Audit trail shows who changed each Flow, Agent, and Record.

Why logs matter

Use Logs to inspect unexpected Flow output and failed Agent executions. Review each step’s input, output, timing, and error details to find the source of the problem.

Review Logs over time to find recurring slow steps, failures for specific inputs, and unexpected model outputs. For example, when you investigate Alex’s failed Flow execution, open the log, select the step marked with an error, and compare its input and output.

View logs

Open Logs from the sidebar. The log list shows recent entries with a name, duration, token count, cost, and timestamp when available. Use the filters to narrow entries by status, type, level, or time range.

Click a row to open its detail panel. The panel shows the entry’s input, output, timing, and error details when available. For an entry with an execution trace, open Trace to inspect iterations, tool calls, and model turns.

What logs capture

Depending on the event, a log entry can include the following details:

  • Status: Shows whether the execution completed, failed, or is still running.
  • Duration: Shows how long the logged operation took.
  • Step details: Show the input and output for each recorded step, including prompt responses, transform results, and tool calls.
  • Error information: Shows the error message and identifies the failed step.
  • Metadata: Shows the processed Record, the model used, and token counts for prompt steps.

When verbose logging is off, the detail view indicates that full outputs, token counts, and cost were not persisted.

Log retention

Logs are retained according to your plan. In Settings, select Billing to check the retention period for your plan.

Recent logs are available immediately. Older entries come from long-term storage. Transactional credential audit entries enter Logs on a one-minute processing cycle, and delivery retries can delay their appearance. If long-term storage is unavailable, the Logs page shows the Historical logs are temporarily unavailable. Showing recent entries only. banner. New entries continue to be recorded, and available history returns after storage recovers.

Next steps

Continue with these guides: