Review stale queue provenance and read-only posture

Problem

You need to understand where stale candidates came from, why the stale queue may be read-only, or what QuillDock will do before any stale delete starts.

Who this is for

Operators reviewing items that exist in Wix CMS but no longer appear in the latest trusted QuillDock source snapshot.

What you will see

• Stale queue shows candidates from the latest trusted snapshot
• candidates stay separate from main publish
• QuillDock requires review and typed confirmation before stale delete can run
• the queue may stay visible but read-only when QuillDock cannot safely start deletes yet

Important behavior

• Main publish is create and update only. It does not delete stale items.
• Stale delete is a separate confirmed run type.
• QuillDock must complete backup-before-delete before it starts removing items.
• Stale candidates come from the latest trusted snapshot, not from an untrusted draft or a failed run.

Why the stale queue may be read-only

• no trusted snapshot exists yet
• the saved configuration changed after the last trusted snapshot
• the trusted snapshot is no longer the right basis for delete review
• the site is in read-only mode because of entitlement state
• stale delete is not enabled for the site yet

Step-by-step review flow

1. Open Stale queue.
2. Review the trusted snapshot context and candidate list.
3. Rerun preflight first if QuillDock says the queue no longer matches the current configuration.
4. Mark only the intended items for review.
5. Type DELETE only when you are ready to queue a separate stale-delete run.

When to contact support

Contact support if the stale queue looks inconsistent with the latest trusted snapshot, if reviewed items still stay blocked after the route says they are ready, or if the queue becomes read-only and the reason is not clear from the route.

Related features and docs

• Stale queue
• Preflight
• Run detail
• Restore from a backup