Understand annotation Undo and Redo
Undo and Redo operate on annotation changes in the active editor. The history is bounded to one hundred recorded annotation changes. A new edit clears the redo branch. Do not treat this history as an unlimited backup of every previous session.
The original capture is retained separately in local history. Restore original is a different action from reversing one annotation. Download a needed edited result before broadly resetting, clearing history or closing work.
Reverse the smallest necessary change
- Identify whether the problem is an annotation, crop or missing original.
- For a recent annotation change, use Undo and inspect the result.
- Use Redo only if the intended redo state is still available.
- For a fresh start, keep required exports and return to the original deliberately.
Keep important outputs outside the editor
The local capture collection is capped at twelve originals. Earlier edited downloads are your separate files. Reopening an original does not promise recovery of a previous editing session. Name and save the useful version before experimenting.
Choose the next step from the actual result
Before trying recovery, inspect what actually remains: the active editor, the local original and any downloads. They are separate resources with different limits. A recent annotation deletion may be reversible in the active editor, while a closed earlier session may require the export you saved. Avoid making many unrelated new edits during diagnosis because they change the available history and make the useful state harder to identify.
When returning to an original, check whether annotations or crops need to be recreated for the intended result. Review one change at a time and save the useful version before experimenting again. If no copy exists, say that plainly and recapture the accessible original page when possible. Do not infer a cloud restore feature from the presence of optional account pages.
A worked example
You delete a label by mistake. Undo that deletion and inspect the restored text before making a new change. If you then draw a new arrow, the old redo branch is cleared. If you wanted a clean start instead, save the useful version first and return to the original deliberately rather than clicking through many uncertain Undo states.
Add your observations. This template processes no files and sends no report.
Check the result
If something is wrong
| Observation | Next step |
|---|---|
| Redo unavailable | A new edit may have cleared its branch; check existing downloads rather than assuming an unlimited recovery history. |
| Previous session edits absent | Use the edited file you saved; original capture history is a different collection. |
| Original was cleared | Check downloaded files; do not assume an unavailable restore service. |
Common questions
Is Undo an unlimited backup?
No. Annotation history is bounded and local to the active editor workflow.
Does history preserve every edited version?
The recent capture collection retains originals separately. Save important edited exports yourself.