Documentation
Docs Run & Operate

Troubleshooting

Fix the most common workflow, auth, variable, queue, and editor issues quickly.

All Levels 6 min Run & Operate
Browse documentation
Run & Operate All Levels 6 min

Troubleshooting & FAQ

Encountering an issue? Most workflow problems can be solved by checking the Execution Inspector. Here are the most common scenarios and fixes.


❌ Workflow Execution Failed

If your workflow stops before finishing, it will show as Failed on the dashboard.

Common Errors*: "Invalid API Key", "Service Not Connected", "Model Overloaded".

  1. Check the Inspector: Click the eye icon (👁️) to see which specific node failed.
  2. Read the Error: Scroll down to the red step and read the error message at the bottom.

🧠 "Out of Sort Memory" (Dashboard Error)

If the dashboard fails to load and mentions "Sort Memory":

  • Cause: This usually happens when you have thousands of executions with very large logs.
  • Fix: The dashboard queries are optimized to avoid this. If it persists, ask an admin to review database size, execution retention, and log growth before deleting any historical records.

🔑 Authentication Errors

If a node fails with a "401 Unauthorized" or "403 Forbidden" error:

  • Fix: Go to the Integrations page and click "Reconnect" for the service being used by that node. Tokens can sometimes expire or be revoked by the external platform.

🔗 Variables are Empty ({{...}})

If your AI Agent says it didn't receive any input, or a variable is blank:

  1. Check IDs: Ensure the node ID in your variable {{nodes.ID.result}} matches exactly.
  2. Verify Path: Ensure the path exists. If you are trying to grab {{input.title}} but the previous node returns {"name": "...", "id": ...}, it will be blank.
  3. Trace the Input: Use the Execution Inspector to see exactly what "Input Data" was passed into the node.

🕒 Workflow is Waiting or Running Too Long

If a workflow stays active longer than expected:

  • Approval Nodes: Check if the execution is Waiting Approval. It must continue through Approve, Reject, or Request Changes.
  • Wait Node: Check if you added a very long Wait timer (e.g., 60 seconds).
  • Technical Pause: If the execution is Paused, use Resume to continue from the saved state.
  • Loop Limits: Custom code or a misconfigured Loop node can still exhaust plan runtime or step limits. Inspect the execution path before increasing limits.

🧩 Editor assets not loading

If /app/ is blank or shows missing JS/CSS:

  • Refresh the page once and try again.
  • If the problem continues, sign out and back in.
  • Try a private/incognito window to rule out an extension or stale browser cache.
  • If the editor still does not load, contact your workspace admin or support. This usually means the workspace deployment needs attention rather than a workflow configuration change.
Related Guides