> For the complete documentation index, see [llms.txt](https://docs.notionapps.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.notionapps.com/automation/testing-preflight-and-repair/draft-vs-published-automation.md).

# Draft vs Published Automation

## Draft vs Published Automation

Draft automation is what the maker is still changing. Published automation is what customers and app users can reach. Keep the two separate in your testing.

### Draft testing

Use draft testing while building:

1. Change the setup.
2. Run validation.
3. Create a test request.
4. Preview as each role.
5. Fix issues.
6. Repeat.

Draft testing is allowed to be messy because it is not public yet.

### Published testing

Published testing should be boring and predictable. After publishing, run a clean test with a new record and a real role. Confirm that published users can start the workflow, see the destination, act on the item, and see the result.

### Common mistake

A maker tests in draft, publishes, and assumes the published app is identical. Always verify the published app if permissions, roles, screen navigation, or custom domains are involved.

### Safe change workflow

1. Make changes in draft.
2. Validate.
3. Test with roles.
4. Publish.
5. Test the published app.
6. Keep the test record or screenshot as proof for customer handoff.