Recovery paths

Recovery paths

Wrong content published

1. Unpublish the affected record when supported.
2. Verify the public route or placement no longer renders the wrong state.
3. Save a corrected draft.
4. Preview and republish.

Tory or LeeAnn need BFD help

Send a short handoff with:

1. CMS section.
2. Record title and slug.
3. Environment: UAT, staging, or production.
4. Expected result.
5. Actual result.
6. Whether it blocks launch, blocks daily publishing, or is a post-launch improvement.
7. Safe screenshot when the screen does not contain personal data, tokens, cookies, Access headers, or subscriber details.

Channel or article route is broken

1. Confirm the Channel is published.
2. Confirm the Article has the intended Channel and slug.
3. Check optional explicit PowerAdvice path fields.
4. Re-preview and verify the public URL.

Homepage placement is wrong

1. Remove or reorder the homepage placement.
2. Check related module item and sidebar-tab records.
3. Preview the homepage.
4. Publish the corrected module/placement state.

Sponsor or ad creative is wrong

1. Disable the creative or campaign if it is public.
2. Correct advertiser, campaign, placement, destination, asset, and alt text fields.
3. Preview the public surface.
4. Reactivate only after sponsor approval.

Image pasted into the editor becomes a placeholder

1. Save the draft without publishing.
2. Upload the image file directly instead of relying on copy/paste.
3. Preview the article or media route.
4. If the fallback remains, capture the record slug, image source, file type, and preview route for BFD.

Content needs to be removed

1. Confirm whether the goal is temporary unpublish, archive, restore later, or permanent deletion.
2. Prefer unpublish/archive when the content may need to return.
3. Verify the public route no longer renders the removed content.
4. Use permanent deletion only when explicitly approved.

Documentation drift is detected

1. Run npm run docs:report.
2. Build a Docs OS update packet from the code change.
3. Update affected docs pages and screenshot manifest entries.
4. Run npm run docs:verify, npm run docs:screenshots:check, and npm run docs:poweradvice:audit.