Versions and deploy
Drafts, immutable versions, deploys, slugs, disabling, duplicating and deleting decisions — and what your API clients see at each step.
Every decision has an editable draft and a history of immutable versions. The API always runs the active version; the draft only reaches production when you deploy it.
Anatomy of a decision
| Property | Rules |
|---|---|
| Name | 1 to 80 characters. |
| Slug | The endpoint: POST /v1/decisions/{slug}. Lowercase letters, digits and single dashes, up to 64 characters. Unique in the workspace. |
| Description | Optional, up to 500 characters. |
| Draft | The schema you are editing. |
| Versions | Immutable snapshots created by each deploy: v1, v2, … |
| Status | Draft, Live or Disabled. |
Lifecycle
Draft ──deploy──▶ Live (v1) ──deploy──▶ Live (v2) ──deploy──▶ …
│ ▲
disable│ │enable
▼ │
Disabled| Status | What POST /v1/decisions/{slug} returns |
|---|---|
| Draft — never deployed | 409 DECISION_NOT_DEPLOYED |
| Live | 200 with the active version's answer; version tells which one |
| Disabled | 409 DECISION_DISABLED |
| Deleted (or unknown slug) | 404 DECISION_NOT_FOUND |
Drafts and auto-save
The editor and the visual builder edit the same draft. Changes are saved automatically about 1.5 seconds after your last edit — only when the draft is valid; otherwise the save bar lists the issues with a Go to error link.
If a teammate (or another tab) saved the decision after you opened it, your save is refused rather than overwriting theirs: the save bar shows Someone else saved this decision and offers Load current version.
Saving a draft never changes production.
Deploy
Deploy (in the decision's Deploy tab) snapshots the current draft as version n + 1 and makes it active immediately — in-flight clients switch to it on their next call. Unsaved edits are saved first; a draft with schema issues can't be deployed.
- Versions are immutable: they can't be edited or deleted.
- The response's
versionfield and every execution record the version that answered. - The Version history lists all versions (Live or Archived) with their full schema.
- A version keeps running as it was deployed. When Dcision tightens a validation rule — v0.3 checks rule values against the options, levels and ranges they compare with — the new rule applies the next time you save or deploy the draft, never to a live version.
- Deploying, like every change to a decision, needs the Member role or higher — see Team, roles and account.
Rolling back
There is no one-click rollback yet. To return to an earlier behavior, open the version's schema in Version history, bring the draft back to it and deploy — this creates a new version number with the old logic.
Slugs
- When you create a decision, the slug is generated from its name: accents removed, lowercase, anything else turned into dashes — "Lead Qualification!" becomes
lead-qualification. If the slug is taken, a suffix is added:lead-qualification-2. - You can change the slug until the first deploy. After that it is locked: clients call it, and a rename would break them (
409 CONFLICT— "The slug can't change after the first deploy."). - Slugs are unique per workspace. Two workspaces can both have a
lead-qualificationdecision: the API key decides which workspace — and so which decision — runs.
Disable and enable
Disable endpoint stops a live decision without losing anything: calls get 409 DECISION_DISABLED until you click Enable endpoint, which serves the same active version again. Only a decision that has been deployed can be enabled.
Duplicate
Duplicate copies the draft (not the versions) into a new decision named "name (copy)", with its own slug and no versions. It counts toward your plan's decision limit.
Delete
Delete removes the decision together with its versions and its execution history. Calls to its slug fail immediately with 404 DECISION_NOT_FOUND, and the slug becomes free for a new decision. This can't be undone.
Plan limits
The number of decisions per workspace depends on the plan — 2 on Genesis, 10 on Developer, unlimited on Growth and Enterprise. Creating or duplicating beyond it fails with 402 PLAN_LIMIT_REACHED; delete a decision or upgrade. Disabled and draft decisions count too.
Confidence and probabilities
What confidence means for each question type on one 0–1 scale, how it affects minConfidence, weighted levels, the full probability distributions and near ties.
Decision settings
engine, storeInput, storeOutput, timeoutMs, fallbackAction and onEngineError — what each runtime setting of a decision does, its default and its limits — plus the workspace settings.