Logs

What are Logs?

Logs give you a detailed record of every Flow and Agent execution in your workspace. Each log entry captures when an execution started, what steps ran, what data flowed between them, and whether it succeeded or failed. Logs also capture your workspace’s change history: the Audit trail shows who changed each Flow, Agent, and Record.

Why logs matter

When a Flow produces unexpected output or an Agent takes a wrong turn, logs are the first place to look. They show you exactly what happened at each step so you can pinpoint the issue without guessing.

Logs also help you understand how your Flows and Agents behave over time. You can spot patterns like consistently slow steps, recurring failures on specific inputs, or unexpected model outputs.

Accessing logs

Go to Logs in the sidebar under Manage. The log list shows recent executions with the Flow or Agent name, status, duration, and timestamp.

Click any row to open the full execution detail, which shows each step’s input, output, and timing.

What logs capture

Each log entry includes:

  • Status — whether the execution completed successfully, failed, or is still running.
  • Duration — how long the execution took from start to finish.
  • Step details — the input and output for each step in the Flow, including prompt responses, transform results, and tool calls.
  • Error information — if a step failed, the error message and which step caused the failure.
  • Metadata — the Record processed (if any), the model used, and token counts for prompt steps.

Log retention

Logs are retained based on your plan. Check your plan details in Settings → Billing for the retention period that applies to your workspace.

Recent log entries are always available immediately, while older entries are served from long-term storage. If long-term storage is briefly unavailable, the Logs page shows a “Historical logs are temporarily unavailable” banner and displays only recent entries until the issue resolves. Nothing is lost during these windows: new entries keep being recorded, and history reappears automatically once storage recovers.

Next steps