Why does my workflow test fail when I select "Draft"?

When you test a workflow, you choose which version to run the test against: the workflow's published version, or its draft version. If you test the draft version of a workflow that's already published, and no one is actively editing it, the test fails right away instead of running. This is expected behavior once you understand how drafts work, and it's easy to fix.

What's the difference between testing "Published" and "Draft"?

When you set up a test, the Version of this workflow to test option lets you choose:

• Published — runs the test against the version currently live for your account.
• Draft — runs the test against an in-progress, unpublished edit to that workflow.

Why does the test fail when I select "Draft"?

A draft only exists while someone is actively editing a workflow and hasn't published those changes yet. Once a workflow is published, that in-progress draft is gone, unless a new edit has been started since. So if the workflow is already live and no one has started a new unsaved edit, there's no draft version to test against, and the test fails immediately instead of evaluating your case.

How do I test a workflow that's already live?

Select Published instead of Draft.

1. Open the workflow and go to the Test tab.
2. Select Test workflow.
3. Under Version of this workflow to test, choose Published.
4. Select at least one test case, then run the test.

This runs the test against the version currently live for your account and returns a normal pass or fail result.

How do I test changes before I publish them?

Start editing the workflow to create a new draft. Once you have an unsaved edit in progress, the Draft option will have something to test against, and you can use it to check your changes before publishing.