Troubleshooting Execution Results

How to read execution logs, identify errors, and fix failed runs.

Written By pvdyck

Last updated About 5 hours ago

Troubleshooting Execution Results

💡 Note:TL;DRIf an agent fails, you will see it in the Execution History. Click the log to see the exact error node. The most common issues are missing API credentials or incorrect input data.

Sometimes, an agent run will fail. Because agents run inside a secure Cloudflare Worker sandbox, we capture detailed logs so you or the Builder can figure out what went wrong.

(Remember: If an agent crashes mid-execution, you are refunded the unused authorization amount. You only pay for what actually ran).

Viewing the Logs

When a run is completed (or fails), you can view its results in the Execution History:

  1. Go to the Executions tab in your Producer Dashboard.
  2. Click on a specific run to open the Execution Results Modal.
  3. Here, you will see a JSON output of the exact path the data took through the workflow.

Common Errors & Fixes

1. Missing Credentials or 401 Unauthorized

  • The Problem: The agent tried to call an external API (like OpenAI) but your API key was missing or invalid.
  • The Fix: Go to your Producer Dashboard, click the Credentials (key) icon for that agent, and ensure your keys are correctly entered and active.

2. Invalid Input Data

  • The Problem: The agent expected specific data in the webhook payload (like "email": "test@example.com") but you provided something else.
  • The Fix: Check the original documentation provided by the Builder to ensure your JSON payload matches the required schema.

3. Execution Timeout (10s limit)

  • The Problem: The agent took too long to run. Our secure sandbox limits HTTP requests to 10 seconds.
  • The Fix: If the external API being called is consistently slow, you may need to ask the Builder to redesign the workflow using an asynchronous pattern.

4. Code / Logic Bug

  • The Problem: The Builder's code threw an unhandled exception.
  • The Fix: This is on the Builder to fix! Builders are incentivized to keep their agents working to earn revenue. Check back later to see if they have pushed an update.

Execution Status Display

All executions that encounter errors display as "Failed" (red) in the Execution History, regardless of error type. Use the "Failed" filter to find all error cases quickly.

Related