Diagnose and resolve common issues with executions, webhooks, deployments, and connections.

When something goes wrong in DRAGOPS, the first step is to narrow down where the problem is. This section covers the most common issues organized by area, with symptoms, causes, and step-by-step solutions.

Quick reference

Use this table to jump to the right page based on what you are experiencing:

Symptom	Page
Pattern fails or produces wrong output	Execution errors
Execution times out	Execution errors
Loop runs forever	Execution errors
Webhook URL returns 404	Webhook issues
Webhook does not trigger the pattern	Webhook issues
Request body is empty in the pattern	Webhook issues
HMAC validation fails	Webhook issues
Deploy fails with errors	Deployment issues
Pattern is deployed but does not run	Deployment issues
OAuth connection fails	Connection issues
API key returns 401	Connection issues

General debugging steps

Before diving into a specific troubleshooting page, try these steps:

Check the execution log. Go to the Deployments page, select the deployment, and open the most recent execution. The node-by-node log shows exactly where the pattern succeeded or failed and what data each node processed.
Verify your wires. Open the pattern in the editor and trace the execution flow from the trigger node to the end. Make sure every required pin is connected and that data types match between connected pins.
Test with sample data. Select Run in the editor toolbar and provide known-good sample data. If the pattern works with sample data but fails in production, the issue is with the incoming data, not the pattern logic.
Add logging. Place Log nodes at key points in your pattern to see intermediate values during execution. Check the console output after a test run to verify data flows as expected.
Check the On Error handler. If your pattern fails silently, add an On Error node to capture unhandled errors and log them. On Error acts as a safety net for any error that is not caught by a Try / Catch node.