Logs

The Logs block queries workflow run logs in the current workspace and fetches full details for individual runs — the same data you see on the Logs page, available to your workflows.

Operations

Find runs matching a set of filters. Returns only the matching run IDs, ordered newest-first by default.

  • Workflows: select specific workflows, or leave empty for all (comma-separated IDs in advanced mode)
  • Status: info, error, running, pending, cancelled (empty for all)
  • Time Range: presets from the past 30 minutes to the past 30 days, or explicit ISO start/end dates in advanced mode
  • Cost: compare run cost against a credit threshold (e.g. ≥ 10 credits)
  • Duration: compare run duration against a millisecond threshold
  • Limit: maximum run IDs to return (default 100, max 200)

Fetch everything about a single run by its run ID:

  • runId, workflowId, workflowName
  • status, trigger, startedAt, durationMs
  • cost: run cost in credits
  • traceSpans: the full trace — per-block inputs, outputs, timings, and tool calls
  • finalOutput: the run's final output

Typical Pattern

Query for the runs you care about, then loop over the returned IDs and fetch details for each:

  1. Query Logs with Status: error and Time Range: Past 24 hours<logs1.runIds>
  2. Loop over the IDs and call Get Run Details → inspect <logs2.traceSpans> to find the failing block
  3. Act on it — post a summary to Slack, file a ticket, or feed the trace to an Agent block for diagnosis

This pairs naturally with the Sim trigger: the trigger hands you the runId that fired the event, and Get Run Details gives you the full trace.

The block always operates on the current workspace. Costs are denominated in credits, both for the cost filter and the cost output.

Common Questions

To keep payloads small and predictable. Run summaries can be large — fetch only the runs you actually need with Get Run Details.
No. The block is scoped to the workspace the workflow lives in.
The execution trace for a run: every block that ran, its inputs and outputs, timings, and any tool calls — the same data shown in the Logs page trace view.
As far as your plan's log retention. Free plans retain logs for 7 days; paid plans retain them indefinitely.

On this page