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
  • Flows
    • What are Flows?
    • Creating and Editing Flows
    • Flow step types overview
    • Agent and Flow Templates
  • Agents
    • What are Agents?
    • Creating and configuring Agents
    • Agent tools
  • Records
    • What are Records?
    • Creating and managing records
  • Tools
    • What are Tools?
    • Built-in Tools
    • Creating custom tools
    • Creating external tools
  • Evals
    • What are Evals?
    • Running an Eval
  • Schedules
    • What are Schedules?
  • Logs
    • What are Logs?
  • Integrations
    • Connecting AI model providers
  • Settings
    • What's in Settings?
    • Available AI models
  • Troubleshooting & FAQ
    • FAQ
    • Rate Limits and Usage
    • Managing Runtype with Claude
Dashboard
LogoLogo
On this page
  • Why logs matter
  • Accessing logs
  • What logs capture
  • Log retention
  • Next steps
Logs

What are Logs?

Was this page helpful?
Previous

Connecting AI model providers

Next
Built with

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.

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.

Next steps

  • Learn how to read step-by-step execution details in Viewing execution logs.
  • Set up live tailing and export logs in Live mode and exporting.
  • Find specific executions in Searching and filtering logs.
  • Troubleshoot issues in Debugging failed executions.