docs: add runbook for recovering pinned Workflows after a bad rollout#4708
Merged
Conversation
Adds a new page covering how to roll back, identify, and recover pinned Workflows affected by a faulty Worker Deployment Version. Covers stopping the rollout, identifying affected Workflows via Search Attributes, choosing between Versioning Override and Reset-with-Move based on Workflow state, handling eventual consistency via drainage status, and cleanup. - New page: docs/production-deployment/worker-deployments/recover-pinned-workflows.mdx - Cross-link from worker-versioning.mdx (Moving a pinned Workflow section) - Cross-link from troubleshooting/index.mdx - sidebars.js: added under Worker deployments Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
|
||
| For a complete runbook covering batch recovery, drainage handling, and how to choose between Versioning Override and Reset-with-Move based on each Workflow's state, see [Recover pinned Workflows after a bad rollout](/production-deployment/worker-deployments/recover-pinned-workflows). | ||
|
|
||
| ## Migrating a Workflow from Pinned to Auto-Upgrade |
Contributor
There was a problem hiding this comment.
📝 [vale] reported by reviewdog 🐶
[Temporal.Headings] 'Migrating a Workflow from Pinned to Auto-Upgrade' should use sentence-style capitalization.
flippedcoder
approved these changes
Jul 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new page covering how to roll back, identify, and recover pinned Workflows affected by a faulty Worker Deployment Version. Covers stopping the rollout, identifying affected Workflows via Search Attributes, choosing between Versioning Override and Reset-with-Move based on Workflow state, handling eventual consistency via drainage status, and cleanup.
┆Attachments: EDU-6527 docs: add runbook for recovering pinned Workflows after a bad rollout