Troubleshooting
Common workflow issues and how to fix them.
Workflows is in Beta. The UI and API may change. The sidebar entry is currently disabled for most workspaces — your account team enables it for pilot orgs.
HTTP request was blocked
The SSRF guard rejected the target host. Blocked targets include private IPv4 ranges, IPv6 ULA and CGN ranges, IPv4-mapped IPv6, multicast, and hosts that resolve to a mix of public and private IPs. Target a public hostname instead. To reach an internal service, route traffic through an authenticated public proxy.
Composio trigger won't enable
The integration connection is inactive or its credentials have expired. Open /settings/integrations, find the integration, and reconnect. The trigger picker only shows active connections — if the integration is missing entirely, connect it first before returning to create the trigger.
Composio trigger creation partially failed
The workflow saved but Composio rejected the subscription. The UI surfaces the orphan trigger ID. Delete the trigger row from the Triggers tab and recreate it — recreating cleanly re-issues the subscription to Composio.
JSONata expression error in Transform
The run detail shows the JSONata cause inline. Common mistakes: referencing a node id that doesn't exist, mismatched brackets, and expecting an array when the upstream value is a plain object. Correct the expression in the Properties drawer and re-run the workflow from the failed node.
Schema validation warning won't go away
The action's input schema has a required field that is still empty. Validation warnings are non-blocking — save the node anyway and fill in the field before publishing. An empty required field causes a run-time failure at the node.
Webhook signature mismatch
The request's HMAC signature doesn't match the trigger's signing secret. Possible causes: the caller has an old or incorrect secret, an intermediary modified the request body, or the secret was rotated after the caller was configured. Re-copy the current secret from the Triggers tab and update the caller.
A run is stuck "Waiting"
Check which node type is holding the run:
- Wait node — the run resumes when the scheduled duration elapses. The scheduled resume time is shown in the run detail.
- Approval node — no one has approved or rejected. Find the pending approval in the global Approvals view and act on it.
- External callback — the upstream service hasn't called back. If you're sure the callback is lost, cancel the run from the run detail page.
Canvas node won't drag or select
Refresh the page. The canvas reacts to prop and state changes and can rarely enter a loop that blocks interaction. A page refresh clears the state cleanly without losing the draft.