Monitor and debug SuperPlane workflow executions. Inspect runs, diagnose failures, and manage execution queues. Use when a workflow fails, an execution is stuck, or the user wants to check run status. Triggers on "debug", "failed", "execution", "run status", "stuck", "queue", "troubleshoot".
Inspect, debug, and manage workflow executions.
| Task | Command |
|---|---|
| List events for canvas | superplane events list --canvas-id <id> |
| Trace an event's executions | superplane events list-executions --canvas-id <id> --event-id <eid> |
| List node executions | superplane executions list --canvas-id <id> --node-id <nid> |
| Cancel execution | superplane executions cancel --canvas-id <id> --execution-id <eid> |
| List queued items | superplane queue list --canvas-id <id> --node-id <nid> |
| Delete queued item | superplane queue delete --canvas-id <id> --node-id <nid> --item-id <iid> |
Before any debugging, confirm the CLI binary is available without requiring network access:
command -v superplane
If this does not print a path: stop and tell the user to install the CLI from https://docs.superplane.com/installation/cli. Debugging requires the CLI to inspect events, executions, and queues.
Then verify the current session:
superplane whoami
If whoami fails because of authentication, DNS, timeout, or connection issues, the CLI is installed but the session is not usable yet. Tell the user to connect, fix the context, or allow network access as needed before debugging through the CLI.
If debugging will require canvas edits, apply them as draft updates:
superplane canvases update <name-or-id> --draft --file canvas.yaml
superplane canvases list
superplane events list --canvas-id <canvas_id>
Each event is a trigger firing that starts a run.
superplane events list-executions --canvas-id <canvas_id> --event-id <event_id>
Look for:
superplane executions list --canvas-id <canvas_id> --node-id <node_id> -o yaml
Check if failures are recurring. For expression errors, inspect the actual payload structure:
rootEvent.data.data — the trigger's real event payload (the double .data is the event envelope wrapping the webhook payload)input — what the node received from its upstream node (also has { data, timestamp, type } envelope)resultMessage — the exact error, including which expression field was nilUse these real payloads to fix expression paths rather than guessing from documentation.
For branching/channel issues, inspect outputs in execution YAML (not just top-level result):
RESULT_PASSED while only emitting on a non-default channel (for example, failed)outputs match edge wiring (success, failed, default, etc.)events list-executions, trust the node's outputs block for routing truthUpdate the canvas, then trigger a new run from the UI or via a manual_run trigger.
superplane canvases update <name-or-id> --draft --file canvas.yaml
Node fails immediately with permission error. Check:
superplane integrations list
superplane secrets list
Verify the integration is connected and the secret is valid.
Node fails referencing a missing field. Check:
$['Node Name']Executions pile up without progressing:
superplane queue list --canvas-id <id> --node-id <nid>
Causes: node is paused, Approval waiting for human input, Time Gate holding, external service unresponsive.
Clear stuck items:
superplane queue delete --canvas-id <id> --node-id <nid> --item-id <iid>
Merge waits for ALL incoming edges. If one branch is stuck, filtered out, or failed, Merge blocks. Check every upstream branch.
| Need | Use Skill |
|---|---|
| Create or modify a canvas | superplane-canvas-builder |
| CLI commands and authentication | superplane-cli |
For agents that can fetch URLs, the full SuperPlane docs are available in LLM-friendly format: