Reference

Logging

Every workflow run is logged. There are two places to read them: the Console for the run you're watching, and the Logs page for everything.

Real-time Console

During manual or chat runs, the Console panel in the editor shows each block as it runs — active-block highlighting, outputs as they complete, per-block timing, and success/error status.

Logs page

Every run from every trigger — manual, API, chat, schedule, webhook — lands on the Logs page, with filtering by time range, status, trigger type, folder, and workflow, full-text search, and a Live mode that streams new entries in as they're recorded.

Log details

Click any entry to open its sidebar: the run's timeline (start/end, total duration, per-block timing) and each block's data flow.

The block's result — JSON-formatted structured data, markdown rendering for AI content, and a copy button.

What the block received — resolved variable values, referenced outputs, and environment variables. API keys are automatically redacted.

Workflow snapshots

View Snapshot opens a frozen copy of the workflow exactly as it was at run time — structure, block states, connections — and each block is clickable to its inputs and outputs. This is how you debug a run of a workflow you've since changed.

Snapshots exist for runs after the enhanced logging system was introduced. Older migrated logs show "Logged State Not Found".

Retention

  • Free: 7 days — logs are archived to cloud storage, then deleted.
  • Pro / Team / Enterprise: retained indefinitely.

Next

Common Questions

Free plans retain logs for 7 days — after that, logs are archived to cloud storage and deleted from the database. Pro, Team, and Enterprise plans retain logs indefinitely with no automatic cleanup.
Each log entry includes the run ID, workflow ID, trigger type, start and end timestamps, total duration in milliseconds, cost breakdown (total cost, token counts, and per-model breakdowns), run data with trace spans, final output, and any associated files. The log details sidebar lets you inspect block-level inputs and outputs.
No. API keys and credentials are automatically redacted in the log input tab for security. You can safely inspect block inputs without exposing sensitive values.
A frozen copy of the workflow's structure (blocks, connections, and configuration) captured at run time, so you can see the exact state behind a particular run — useful for debugging workflows that have been modified since.
Yes. The External API provides endpoints to query logs with filtering by workflow, time range, trigger type, duration, cost, and model. You can also set up webhook, email, or Slack notifications for real-time alerts when runs complete.
It refreshes the Logs page in real time so new entries appear as they are recorded — useful during deployments or when monitoring active workflows.

On this page

Real-time Console
Logs page
Log details
Workflow snapshots
Retention
Next