Documentation
HomeAPISign In
  • Getting Started
    • Overview
      • Core Concepts
      • Building your First Workflow
    • API Reference
  • Your Data
    • Brand Kits
    • Knowledge Bases
      • Add Data
        • Upload Files
        • Web Scrape
        • Import from Google Drive
        • Import from SQL Database
        • Import from Shopify
      • Knowledge Base Search
      • Knowledge Base Metadata
      • Knowledge Base API
  • Building Workflows
    • Workflow Concepts
      • Workflow Inputs
        • Input Types
      • Workflow Outputs
      • Variable Referencing
      • Liquid Templating
    • Workflow Steps
      • AI
        • Prompt LLM
          • Model Selection Guide
          • Prompting Guide
        • Transcribe Audio File
      • Web Research
        • Google Search
        • Perplexity Deep Research
        • Web Page Scrape
      • Code
        • Run Code
        • Call API
        • Format JSON
        • Run SQL Query
        • Write Liquid Text
      • Flow
        • Condition
        • Iteration
        • Human Review
        • Content Comparison
        • Error
      • Data
        • Read from Grid
        • Add Rows in Grid
        • Search Knowledge Base
        • Write to Knowledge Base
        • Get Knowledge Base File
      • AirOps
        • Workflow
        • Agent
      • Image & Video
        • Generate Image with API
        • Search Stock Images
        • Fetch Stock Image with ID
        • Resize Image
        • Screenshot from URL
        • Create OpenGraph Image
        • Create Video Avatar
      • SEO Research
        • Semrush
        • Data4SEO
      • Content Quality
        • Detect AI Content
        • Scan Content for Plagiarism
      • Content Processing
        • Convert Markdown to HTML
        • Convert PDF URL to Text
        • Group Keywords into Clusters
      • B2B Enrichment
        • Hunter.io
        • People Data Labs
      • CMS Integrations
        • Webflow
        • WordPress
        • Shopify
        • Contentful
        • Sanity
        • Strapi
      • Analytics Integrations
        • Google Search Console
      • Collaboration Integrations
        • Gmail
        • Google Docs
        • Google Sheets
        • Notion
        • Slack
    • Power Steps
    • Testing and Iteration
    • Publishing and Versioning
    • Logs
    • Studio Toolbar
  • Running Workflows
    • Run Once
    • Run in Bulk (Grid)
    • Run via API
    • Run via Trigger
      • Incoming Webhook Trigger
      • Zapier
    • Run on a Schedule
    • Error Handling
  • Grids
    • Create a Grid
      • Import from Webflow
      • Import from Wordpress
      • Import from Semrush
      • Import from Google Search Console
    • Add Columns in the Grid
    • Run Workflows in the Grid
      • Add Workflow Column
      • Run Workflow Column
      • Schedule Workflow Column
      • Map Workflow Outputs
      • Review Workflow Run Metadata
    • Review Content in the Grid
      • Review Markdown Content
      • Review HTML Content
      • Compare Content Difference
    • Publish to CMS from Grid
    • Pull Analytics in the Grid
    • Searching and Filtering
    • Export as CSV
  • Copilot
    • Chat with Copilot
    • Edit Workflows with Copilot
    • Fix Errors with Copilot
  • Monitoring
    • Task Usage
    • Analytics
    • Alerts
    • Execution History
  • Your Workspace
    • Create a Workspace
    • Folders
    • Settings
    • Billing
    • Use your own LLM API Keys
    • Secrets
    • Team and Permissions
  • Chat Agents (Legacy)
    • Agent Quick Start
    • Chat Agents
    • Integrate Agents
      • Widget
      • Client Web SDK
  • About
    • Ethical AI and IP Production
    • Principles
    • Security and Compliance
Powered by GitBook
On this page
  • What are Workflow Logs?
  • Why Logs Matter for Your Workflows
  • Where to Find Logs
  • Loading Executions into Studio
  • Best Practices for Using Logs

Was this helpful?

  1. Building Workflows

Logs

Last updated 2 days ago

Was this helpful?

What are Workflow Logs?

Workflow Logs provide a detailed, step-by-step record of everything that happens during a workflow execution. They capture the complete journey of your data through each step of your workflow, including:

  • Step execution details: Runtime duration, success/failure status, and number of tasks processed

  • Input and output data: The exact data that went into each step and what came out

  • Metadata: Information about who ran the workflow, when it was executed, and from what source

  • Error messages: Detailed error information when steps fail, helping you identify and fix issues

Why Logs Matter for Your Workflows

  • Understand workflow behavior: See exactly what data flows into and out of each step

  • Debug failed executions: Identify where and why workflows fail with detailed error messages

  • Optimize performance: Find bottlenecks by reviewing step execution times

  • Iterate without re-running: Load any past execution into Studio with all outputs intact

Where to Find Logs

  • Studio Testing Mode: Click on the History icon on the top right of the Studio to view the Logs that workflow's executions

  • Workflow History: Access all past executions via the "History" tab in your workflow

  • Grid Workflow Columns: Click any cell in the workflow column to view logs for that specific row's run

Loading Executions into Studio

The "Open in Studio" button lets you load any previous workflow execution back into the Studio with all step outputs restored. This powerful feature enables you to:

  1. Debug issues without re-running the entire workflow

  2. Test changes using real data from actual executions

  3. Skip waiting for external API calls or long-running processes

  4. Iterate on prompts and logic with production data

To use it: Simply click "Open in Studio" from any execution's log view. The Studio will load with all intermediate outputs populated, allowing you to modify and test any step immediately.

This is especially valuable for debugging complex workflows, working with time-sensitive data, or collaborating on workflow improvements.

Best Practices for Using Logs

  1. Use Descriptive Step Names: Give your steps clear, descriptive names to make logs easier to navigate and understand

  2. Monitor Execution Times: Keep an eye on step durations to catch performance degradation early

By leveraging the full power of Logs, you can build more reliable workflows, debug issues faster, and continuously improve your automation processes.