For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Dashboard
User GuideDeveloper GuidesAPI Reference
User GuideDeveloper GuidesAPI Reference
  • Getting Started
    • What is Runtype?
    • Creating your account
    • Platform Keys vs. BYOK
    • Understanding the Runtype UI
    • Quickstart: Social Media Post Generator
    • Quickstart: From Agent to Chat Widget
  • Dashboard
    • What is the Dashboard?
    • Daily Executions
  • Playground
    • What is the Playground?
  • Products & Surfaces
    • What are Products?
    • What are Surfaces?
    • Creating a Product
    • Setting up a Chat Surface
    • Setting up an API Surface
    • Setting up an MCP Surface
    • Setting up an A2A Surface
    • Setting up a Slack Surface
    • MCP authentication
    • Authenticating with product API keys
    • Embedding the chat widget (script tag)
    • Embedding the chat widget (React)
    • Surface orchestration modes
    • Product views
    • Adding Capabilities to a product
    • Connecting external agents
    • How A2A works
    • Connecting to Cursor / VS Code
    • Connecting to Claude Desktop
    • Scoping API keys to capabilities
    • Auto-generated OpenAPI spec
    • Calling your API endpoints
    • Client tokens and domain restrictions
    • AI-powered theme generation
    • Widget theming and customization
    • Product versioning and status
  • Flows
    • What are Flows?
    • Creating and Editing Flows
    • Flow step types overview
    • Agent and Flow Templates
    • Using prompt steps
    • Using transform-data steps
    • Using conditional steps
    • Using fetch-url and api-call steps
    • Using record steps (upsert/retrieve)
    • Flow variables and templates
    • Flow versioning and publishing
    • Running flows in batch
    • Handling batch failures
    • Debugging flows
  • Agents
    • What are Agents?
    • Creating and configuring Agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
    • Using records in flows
    • Filtering and searching records
  • Tools
    • What are Tools?
    • Built-in Tools
    • Creating custom tools
    • Creating external tools
    • Runtime tools
  • Evals
    • What are Evals?
    • Running an Eval
    • Interpreting eval results
  • Schedules
    • What are Schedules?
    • Automating batch processing
  • Logs
    • What are Logs?
    • Working with Logs
  • Integrations
    • Connecting AI model providers
    • Slack integration
    • Google Workspace integration
    • GitHub integration
    • Linear integration
    • Weaviate (vector search)
    • Firecrawl (web scraping)
    • Exa (web search)
  • Settings
    • What's in Settings?
    • Available AI models
    • What are Organizations?
    • Managing AI models
    • Managing API keys
    • Billing and plans
    • Usage data
    • Team members and permissions
    • Appearance and preferences
    • Integrations (PostHog, Weaviate, Daytona)
  • Troubleshooting & FAQ
    • FAQ
    • Rate Limits and Usage
    • Managing Runtype with Claude
    • Flow execution failures
    • Common errors and solutions
    • Authentication issues
Dashboard
LogoLogo
On this page
  • Viewing execution details
  • Agent executions
  • Searching and filtering
  • Filtering options
  • Search
  • Live mode
  • Exporting logs
  • Debugging failed executions
  • Identifying the failed step
  • Common failure patterns
  • Re-running after a fix
  • Next steps
Logs

Working with Logs

Was this page helpful?
Previous

Connecting AI model providers

Next
Built with

The Logs page is where you investigate what happened during Flow and Agent executions. Every execution produces a log entry with a step-by-step breakdown you can drill into.

Viewing execution details

Click any row in the Logs list to open the execution detail view:

  • Timeline — each step in execution order with status indicators and duration.
  • Step inspector — select a step to see its full input, output, and configuration.
  • Token usage — for prompt steps, the number of input and output tokens consumed.

Agent executions

Agent logs show each iteration of the agent loop, including tool calls, tool results, and the agent’s reasoning at each turn. This helps you understand why the agent chose specific tools and how it arrived at its final response.

Searching and filtering

Use search and filters to find specific executions in your log history.

Filtering options

  • Flow or Agent — narrow to executions of a specific Flow or Agent.
  • Status — show only successful, failed, or in-progress executions.
  • Date range — limit results to a specific time window.

Search

Use the search bar to find executions by keywords in the execution data, including Record metadata and step outputs.

Live mode

Toggle Live in the Logs view to see new executions appear as they start and complete. This is useful when testing a Flow or monitoring a scheduled batch run.

Live mode automatically pauses when you scroll up to review older entries and resumes when you scroll back to the bottom.

Exporting logs

Use the export action to download log data as JSON. Exports include the execution metadata, step details, and timing information for each entry in your current filtered view.

Debugging failed executions

When a Flow or Agent execution fails, logs show you exactly which step caused the failure and why.

Identifying the failed step

Open a failed execution and look for the step marked with an error status in the timeline. The step inspector shows the error message and the input that caused the failure.

Common failure patterns

PatternCauseFix
Model errorsRate limits or invalid API keyCheck your model configuration in Settings
Transform errorsJavaScript error in a transform-data stepReview the script and the input data it received
Fetch errorsExternal API timeout, auth failure, or unexpected response formatVerify the URL, credentials, and expected response shape
Record errorsupsert-record step received non-JSON dataEnsure the source variable contains a JSON object, not a plain string

Re-running after a fix

After fixing the issue, re-run the Flow manually from the Flows page or wait for the next scheduled execution if the Flow is on a Schedule.

Next steps

  • Debugging flows for step-level troubleshooting
  • Flow execution failures for common error patterns
  • What are Logs? for a high-level overview