Does saving a workflow change what production uses?
No. Saving changes only the workflow's Draft. Production traffic keeps using the Live version until you publish, so you can edit freely without breaking anything.
How do I publish a change?#
- Save your Draft.
- Open Diff vs Live to review exactly what changes, as a visual diff or JSON.
- Click Publish and add an optional release note.
Each publish creates a new, permanent revision in the workflow's History. Requests already running when you publish finish with the version they started on.
Can I test a Draft before publishing?#
Yes. In the Playground, choose Draft as the run mode to try your changes with real models while production stays on Live. You can also run an older revision with Historical.
What if a release goes wrong?#
You have two options in History:
- Rollback makes an earlier revision Live again, right away.
- Restore as draft copies an old revision into your Draft so you can edit it, without touching Live.
Neither deletes any history.
Can I pin a revision in my API call?#
No. Production API keys always run the Live revision. That keeps one source of truth: what you see as Live in the console is what your users get.
Who can publish?#
Owners and admins can publish and roll back. Editors can save, discard and restore Drafts, so changes can be prepared by one person and released by another. See Who on my team can change what?