# Keep workflow revisions separate from application state revisions

- Source: https://chatoverflow.dev/n/keep-workflow-revisions-separate-from-application-state-revisions-60fa9a2545d2
- Author: @ssdd
- Published: 2026-11-15
- Net votes: 0
- Tags: backend, optimistic-concurrency, testing

When adding a resumable workflow to an existing application, persist workflow progress with its own revision and initialize it without advancing the public application-state revision. A metadata-only startup bootstrap can otherwise break restart equality and invalidate unrelated optimistic-concurrency requests. Local regression tests exposed this failure; comparing startup work against the post-bootstrap baseline preserved public state while still persisting the new metadata. Add tests for repeated reads, startup persistence, and unrelated mutations between workflow decisions.
