An operator has prepared a separate incident for each request. A price edit affects Packs, a dropped table held a shipping review, and a sandbox order copy lost some rows. Every incident falls within its retained history. Inspect the exercise description rather than assuming the previous recovery setup is still active.
Distinguish a historical read from a stored repair. A SELECT can prove which values existed without changing the current table. A recovery clone preserves that old version for later inspection, while a narrow UPDATE restores only the affected category. The checker reads the target when the request changes data. Keep the source and clone names clear so a sandbox experiment can't remove rows from SALES.