Runbooks and deployments define their processes in exactly the same way. However, where a deployment has a release, a runbook has what is called a Snapshot.
For a given runbook, you can have two snapshots:
Similar to releases, the version of any packages that are used in the runbook are also snapshotted. This means if a newer version of the package is uploaded, and you wish to use it in your runbook, you need to create a new snapshot of the runbook.
A draft snapshot of a runbook is exactly what it sounds like, a draft version of the currently published version. Drafts are meant to give you a place to work and save a runbook that is a work in progress or has not yet been approved for general use.
Draft snapshots can’t be used to create a scheduled runbook trigger, only published snapshots can.
The concept of a published snapshot is designed to help avoid confusion when selecting a version of the runbook you’re supposed to run if you’re not the author. You can think of it as the “Production” ready version of the runbook, which has been approved for general use.
Publishing makes a runbook available to scheduled triggers and consumers (anyone with an appropriately scoped
RunbookRunCreate permission, but without the
RunbookEdit permission). Triggers and consumers will always execute the published snapshot.
The published snapshot contains the process, variables, and packages. This allows editing and testing the runbook without impacting the published version.
Publishing a snapshot
To publish a snapshot, click the publish button on the task page after executing a runbook, or click publish on the runbook’s process page.
Publish from completed task:
Publish from process:
When a producer (anyone with an appropriately scoped
RunbookEdit permission) executes a runbook, they will have the option between executing the published version or the current draft.
Running the current draft allows testing changes before publishing. The latest version of the process and variables will be used and package versions will be prompted for.
Help us continuously improve
Please let us know if you have any feedback about this page.
Page updated on Sunday, January 1, 2023