How to Restore a Discarded Quick Draft
Discarding a quick draft in the Supervisor review queue has never deleted it — the row, its body, and the note explaining why it was set aside all stay in place. Nothing in the queue used to say so, though, which made “Discard” feel final and clearing a queue of a few hundred drafts feel like throwing work away. The Supervisor History view makes that recoverability visible, and gives you a way to act on it.
Where to find it
Open Supervisor → History. This is the archive for review decisions, including quick drafts that were dismissed individually, rejected, or cleared in bulk.
The Review feed is now reserved for active review work: pending drafts that still need a decision, plus raw material under Handovers and drafts. Once a quick draft is discarded, it leaves that active feed and moves into History instead of appearing in a recovery list at the bottom of the queue.
In History, look for the discarded draft you want to recover. Each archived draft row shows the context you need to decide whether to bring it back, including:
- A one-line summary of the draft, such as its diff summary or a fallback label if it doesn’t have one
- The review note explaining why it was set aside — for example, a note left when it was cleared in bulk
- A Restore button, when that draft can still be restored
History keeps these rows because nothing was deleted. It is a record of past review decisions, not more work waiting for you, so discarded drafts don’t compete for attention with drafts that are still pending review.
Restoring a draft
Click Restore on any restorable draft in History. That draft:
- Moves back to pending, so it reappears in the main review queue
- Loses its old review note and reviewer — restoring clears the record of why it was discarded, since it’s headed back into review from scratch
- Reopens its group, if the group had been closed
That last point matters if the draft you’re restoring was the last one in its group. A group with no drafts left in play gets closed automatically, and a closed group is hidden from every list in the queue. Restoring a draft that belonged to a closed group brings the group back too — otherwise the restored draft would come back to pending while its own group stayed invisible everywhere else.
What can and can’t be restored
Only drafts in dismissed or rejected status can come back through History. A deployed draft — one that was already published — can’t be restored, because that draft is now live configuration. Offering it back as a draft and publishing it again would create a second copy of an article the tenant already has. If you need to change something about a deployed article, that’s an edit to the live article itself, not a restore.
Attempting to restore a draft that’s already been restored, or that’s deployed, is refused rather than silently ignored — you’ll see an error rather than a draft quietly staying put.
Why this exists
History is the safety net a bulk clear needs. Before you clear a large queue, it’s worth knowing that every row you clear lands there first, with the reason attached, and that any one of them is a single click away from being back in front of you.