DRAGOPS
DRAGOPS
DocumentationTroubleshootingDeployment issues

Deployment issues

Fix deployment failures — compilation errors, unresponsive patterns, and redeployment problems.

Deployment issues prevent your pattern from going live or from responding to triggers after deployment. Most deployment problems are caught at compile time with clear error messages, but some only surface when the deployed pattern receives real traffic.

Deploy fails

Symptom

You select Deploy in the editor and the deployment does not succeed. An error message appears in the editor.

Cause

DRAGOPS compiles the pattern graph before deployment. Compilation checks for structural issues that would prevent the pattern from executing correctly. Common compilation errors include:

  • Missing trigger node. Every pattern needs at least one trigger node (On Webhook, On Schedule, On Pattern Call, or another event node). Without a trigger, the pattern has no entry point.
  • Unconnected required pins. A node has a required input pin that is not wired to anything.
  • Invalid wires. A wire connects two pins with incompatible data types that cannot be automatically converted.
  • Disconnected execution flow. Impure nodes (nodes with execution pins) must be connected in a chain. If a node's execution input pin is not wired, it never runs.

Solution

  1. Read the error message. The editor shows which node or wire caused the failure. Select the highlighted node to see details in the Inspector Panel.

  2. Fix the reported issue. Connect missing wires, add a trigger node, or remove invalid connections as indicated by the error.

  3. Test before redeploying. After fixing the issue, select Run in the toolbar and provide sample data. Verify the pattern executes successfully in test mode before deploying again.

  4. Check for disconnected nodes. Impure nodes that are not connected to the execution flow do not cause compile errors, but they also never run. Trace the execution flow from the trigger to make sure every node you intend to run is wired into the chain.

Pattern deploys but does not respond

Symptom

The deployment succeeds and shows as Active on the Deployments page. However, when you send a trigger event (a webhook request, a schedule firing, or a pattern call), nothing happens. No execution appears in the history.

Cause

The trigger type does not match the incoming event. For example:

  • The pattern has an On Schedule trigger, but you are sending an HTTP request to the webhook URL
  • The pattern has an On Webhook trigger, but the URL the external service calls belongs to a different pattern
  • The pattern has an On Pattern Call trigger, but no other deployed pattern is calling it

Solution

  1. Verify the trigger type. Open the pattern in the editor and check which trigger node it uses. Make sure the event you expect matches the trigger type.

  2. For webhook triggers: Copy the URL from the Triggers page and compare it to the URL configured in the external service. Each On Webhook node has its own unique URL.

  3. For schedule triggers: Check the cron expression in the On Schedule node. Go to the deployment detail page to verify the next scheduled execution time.

  4. For pattern call triggers: Verify the calling pattern is deployed and that the Call Pattern node references the correct pattern by name.

  5. Check the request log. Go to the Triggers page and open the Request Log tab for the webhook. If requests are arriving but being rejected, the log shows the reason.

Redeployment does not pick up changes

Symptom

You edit a pattern and redeploy it, but the deployed version still uses the old behavior. Changes you made in the editor do not appear to take effect.

Cause

The pattern was not saved before redeployment. DRAGOPS deploys the last saved version of the pattern graph. If you make changes in the editor but do not save before selecting Deploy, the deployed version uses the previous save.

Solution

  1. Save before deploying. After making changes in the editor, save the pattern first (Ctrl+S or Cmd+S), then select Deploy.

  2. Verify the deployment version. Go to the deployment detail page and check the version number. Each deployment increments the version. If the version number did not change, the deployment may not have replaced the previous version.

  3. Test the changes. After redeploying, trigger the pattern with a test event and check the execution log to confirm the new behavior is active.

Webhook URL changes after redeploy

Symptom

You expect the webhook URL to change after redeploying, or you are concerned that redeployment will break your external service's webhook configuration.

Cause

This is not actually a problem. Webhook URLs in DRAGOPS are assigned to the pattern, not to a specific deployment version. The URL is stable across the full deployment lifecycle.

Solution

No action needed. Your webhook URL does not change when you:

  • Redeploy the pattern
  • Undeploy and redeploy the pattern
  • Edit and save the pattern

External services that call your webhook URL do not need to be updated after redeployment. The URL remains the same for the lifetime of the pattern.

See Webhooks for more details on URL stability.

Pattern shows as deployed but nothing runs

Symptom

The deployment appears on the Deployments page with Active status, but no executions are recorded. Triggers that should fire do not produce any executions.

Cause

The deployment may be paused, or the trigger configuration may not match the incoming events.

Solution

  1. Check if the deployment is paused. A paused deployment shows as Active in some views but does not process events. Go to the deployment detail page and look for a Paused indicator. If paused, select Resume.

  2. Check the trigger configuration. Open the pattern in the editor and verify the trigger node is configured correctly:

    • On Webhook: Verify the URL is registered with the external service.
    • On Schedule: Verify the cron expression is correct and the next scheduled time has not passed yet.
    • On Pattern Call: Verify the calling pattern is deployed and running.

  3. Send a manual test. For webhook-triggered patterns, send a curl request directly to the webhook URL and check whether an execution appears:

curl -X POST https://your-webhook-url \
  -H "Content-Type: application/json" \
  -d '{"test": true}'

  1. Check the request log. Go to the Triggers page and open the Request Log tab. If requests are reaching DRAGOPS but being rejected (due to HMAC failure, rate limiting, or other reasons), the log shows the rejection reason.

  2. Redeploy. If the deployment appears active but is not responding, try undeploying and redeploying the pattern. This reregisters the trigger with the execution engine.

Webhook issues

Fix webhook delivery failures — 404 errors, empty payloads, HMAC failures, timeouts, and tap mode.

Connection issues

Fix OAuth failures, expired API keys, and credential management problems.

On this page

Deploy failsSymptomCauseSolutionPattern deploys but does not respondSymptomCauseSolutionRedeployment does not pick up changesSymptomCauseSolutionWebhook URL changes after redeploySymptomCauseSolutionPattern shows as deployed but nothing runsSymptomCauseSolutionRelated