divedra-troubleshooting

name	divedra-troubleshooting
description	Use when diagnosing failed, paused, stalled, timed out, or surprising divedra workflow executions. Applies to session status/progress/logs/export, runtime artifacts, node execution records, workflow validation failures, backend invocation errors, timeout failures, GraphQL inspection, event receipts, and artifact/session-store path issues.
metadata	{"short-description":"Troubleshoot divedra runs"}

Divedra Troubleshooting

Use this skill when a divedra workflow does not behave as expected.

First Commands

divedra workflow validate <workflow-name> --workflow-root <root>

divedra session status <session-id> --output json

divedra session progress <session-id>

Read references/troubleshooting.md for triage by symptom.

Rules

• Fix validation failures before diagnosing runtime behavior.
• Prefer JSON status/export for machine comparison.
• Check workflow root and scope resolution before assuming a workflow changed.
• Use mock scenarios to isolate backend failures from workflow graph failures.
• Check artifact/session roots when outputs or logs seem missing.