AgentLoops
Workflows

Execution Details

View and understand your workflow execution results

Execution Details

Every time you run a workflow, AgentLoops saves a complete record of what happened. The Execution Details page shows you exactly how your workflow ran, what outputs were produced, and where any errors occurred.

Accessing Execution Details

You can view execution details in several ways:

From the Workflow Page

  1. Navigate to your workflow's page
  2. Click on the "Executions" tab
  3. Click on any execution in the list

From the Dashboard

  1. Go to your dashboard
  2. Find recent executions in the activity feed
  3. Click on an execution to view its details

After Running a Workflow

When you run a workflow from the Builder, you'll be automatically taken to the execution details page when it completes.

Understanding the Execution Details Page

The Execution Details page has several sections that help you understand what happened during your workflow run.

Execution Header

At the top of the page, you'll see:

Execution Status Badge Shows the overall status of your workflow execution:

  • Success (green): All nodes completed successfully
  • Failed (red): One or more nodes failed
  • Running (blue): Execution is currently in progress
  • Stopped (gray): Execution was manually stopped

Link to Workflow Click "View Workflow Details →" to navigate back to the workflow's main page.

Workflow Preview

A visual representation of your workflow with execution status overlays:

What You'll See:

  • All nodes from your workflow
  • Color coding showing which nodes succeeded or failed
  • Connection lines showing the flow of data
  • Real-time updates if the workflow is still running

Interactive Features:

  • Click on any node to jump to its execution details below
  • Zoom in/out to see the full workflow
  • Pan around to view large workflows

Execution Metadata

Key information about the execution:

Workflow Name The name of the workflow that was executed (click to open in Builder)

Executed By Shows who or what triggered the execution:

  • User avatar and name for manual runs
  • System indicator for scheduled/automated runs

Started At The exact date and time when the execution began (formatted as: MMM dd, yyyy HH:mm:ss)

Duration How long the execution took to complete:

  • Shown in hours, minutes, and seconds
  • Example: "2m 34s" or "1h 15m 22s"
  • Shows "N/A" if the execution is still running

Succeeded Number of nodes that completed successfully

Failed Number of nodes that encountered errors

Estimated Credits The estimated cost in credits before execution (based on configuration)

Actual Credits The actual credits consumed during execution (only shown after completion)

Execution Results Sections

Outputs Section

This section displays results from Output Nodes in your workflow. Output nodes are specifically designed to capture and display important results.

For Text Outputs:

  • Shows the output node's name
  • Displays the text content
  • Formatted for easy reading

For File Outputs:

  • Shows the file name
  • Provides download link
  • Displays file metadata (type, size, etc.)

Errors Section

If any nodes failed, they'll appear in this section:

What You'll See:

  • Node name that failed
  • Error message explaining what went wrong
  • Timestamp of when the error occurred
  • Input data that was being processed when the error occurred

Common Error Types:

  • Configuration Error: Missing or invalid node settings
  • API Error: Issues connecting to external services
  • Validation Error: Input data doesn't match expected format
  • Timeout Error: Node took too long to execute
  • Credit Error: Insufficient credits to complete operation

Node Execution Details

This section shows every node that ran in your workflow, including:

For Each Node:

  • Node Name: The name you gave the node
  • Node Type: What kind of node it is (e.g., "LLM Chat", "Text Transform")
  • Status: Success, Failed, or Skipped
  • Duration: How long this specific node took to execute
  • Input Data: What data the node received
  • Output Data: What the node produced

Expandable Cards: Click on any node card to expand it and see:

  • Full input values
  • Complete output results
  • Detailed error messages (if failed)
  • Execution metadata

Using Execution Details

Debugging Failed Workflows

When a workflow fails, use the Execution Details page to:

  1. Find the problem: Check the Errors section to see which node failed
  2. Understand the cause: Read the error message and review the input data
  3. Fix the issue: Go back to the Builder and adjust the node configuration
  4. Re-run: Execute the workflow again to verify the fix

Analyzing Performance

Use the duration metrics to:

  • Identify slow nodes that might need optimization
  • Understand which operations take the most time
  • Plan workflow improvements

Verifying Outputs

Use the Outputs section to:

  • Confirm your workflow produced the expected results
  • Download generated files
  • Share results with others

Tracking Credit Usage

Monitor the credit information to:

  • Understand the cost of running your workflow
  • Compare estimated vs. actual credits
  • Optimize workflows to reduce credit consumption

Loop Mode Executions

When viewing execution details for workflows that used Loop Mode, you'll see:

Multiple Iterations: Each node that ran in loop mode will show results for every iteration:

  • Iteration 1: Input → Output
  • Iteration 2: Input → Output
  • Iteration 3: Input → Output

Array Outputs: Instead of single values, you'll see arrays of results:

Output: [Result 1, Result 2, Result 3, ...]

Individual Failures: If one iteration fails, you'll see which specific item caused the error while others may have succeeded.

Execution History

All executions are saved and can be accessed anytime:

Finding Past Executions:

  1. Go to your workflow's page
  2. Click the "Executions" tab
  3. Browse through all past runs

Filtering Executions:

  • View by date range
  • Filter by status (success, failed, etc.)
  • Sort by duration or date

Comparing Executions: You can view multiple execution details side-by-side to:

  • See how changes affected results
  • Compare performance over time
  • Track improvements or regressions

Real-Time Updates

If you're viewing an execution that's currently running:

Live Status Updates:

  • The status badge updates as the workflow progresses
  • Nodes light up as they complete
  • Results appear as soon as they're available

Refresh: The page automatically refreshes to show the latest status. You don't need to manually reload.

Tips for Reading Execution Details

Focus on Outputs First

Start by checking the Outputs section to see if your workflow produced the expected results. This gives you a quick pass/fail understanding.

Check Duration for Bottlenecks

If your workflow is slow, look at individual node durations to find bottlenecks. The slowest nodes are candidates for optimization.

Review Errors Carefully

Error messages often contain the exact information needed to fix problems. Read them thoroughly before making changes.

Compare Iterations in Loops

When using loop mode, compare results across iterations to ensure consistency and catch any anomalies.

Use Execution Details for Learning

Even successful executions can teach you:

  • What data flows through your workflow
  • How long different operations take
  • How much credit different nodes consume

Common Patterns

Successful Execution

  • Status: Success (green)
  • All nodes show success
  • Outputs section has expected results
  • No errors section

Partial Failure

  • Status: Failed (red)
  • Some nodes succeeded, some failed
  • Errors section shows which nodes failed
  • Outputs may be incomplete

Complete Failure

  • Status: Failed (red)
  • Early node failed, preventing others from running
  • Few or no outputs
  • Clear error message in Errors section

Long Running Execution

  • Status: Running (blue)
  • Some nodes completed, others still processing
  • Partial results visible
  • Duration continues to increase

Next Steps

Now that you understand execution details:

On this page