What is a deployment?

A deployment is the live, running version of a pattern. When you deploy a pattern, DRAGOPS compiles the graph into an optimized execution plan, registers its triggers, and makes it ready to handle events.

Until you deploy, a pattern only exists as a draft in the editor. Deploying is what brings it to life.

Deployment lifecycle

A deployment moves through these states:

Deploy → Active → Pause / Resume → Redeploy → Undeploy

Active

The default state after deployment. The pattern is live and responding to triggers. Webhook URLs accept requests, schedules fire on time, and other patterns can call it.

Paused

A deployment can be paused manually or automatically. When paused, triggers stop firing — webhooks return an error, schedules skip, and pattern calls fail gracefully. The deployment remains registered but inactive.

Automatic pausing can occur if the pattern hits error thresholds (circuit breaker). You can resume a paused deployment from the dashboard at any time.

Undeployed

When you undeploy a pattern, it is removed from the execution engine entirely. The graph and all editor state remain intact — you can redeploy at any time.

What happens when you deploy

When you select Deploy in the editor, DRAGOPS:

Compiles the graph — validates the node connections, resolves types, and generates an optimized execution plan
Assigns a version — each deployment gets an incrementing version number for tracking
Registers triggers — webhook URLs are activated, cron schedules are registered, and pattern call endpoints become available
Pushes to the execution engine — the compiled code is loaded and ready to handle events

If compilation fails (for example, due to unconnected required pins or type mismatches), the deployment does not proceed and you see the errors in the editor.

Webhook URL stability

Webhook URLs are assigned to the pattern, not to a specific deployment version. This means:

Your webhook URL stays the same across redeploys
External services that call your webhook do not need to be updated when you redeploy
URLs survive undeploy and redeploy cycles

Versioning

Every deployment creates a new version number. You can view the version history for any pattern in the dashboard. This gives you a clear audit trail of what was deployed and when.

Monitoring deployments

Once deployed, you can monitor a pattern from the dashboard:

Execution history — see every execution with status, duration, and logs
Health indicators — view success and error rates at a glance
Trigger activity — see when triggers last fired and how often

Patterns — what you deploy
Triggers — what fires on a deployed pattern
Executions — the runs a deployment produces

Deployments