Where: Session details → Reject session; Rejected tab → Restore / Delete permanently / Delete all rejected.
How to use it
- Reject moves a record to Rejected instead of immediately destroying it. Use Undo when offered or open Rejected later.
- Restore returns a rejected Session to ordinary browsing. It does not recreate detailed traces previously removed by storage retention.
- Delete permanently requires the destructive confirmation for rejected data. Check the selected records carefully before confirming.
- Delete all rejected / bulk deletion affects the rejected records selected by that action. Export a usable package first when you want an independent backup.
Options and defaults
Reject session
- Default
- Normal disposition
- Options
- Reject / Undo
- Meaning
- Reversible move
Restore to Sessions
- Default
- Only in Rejected
- Options
- Restore
- Meaning
- Keeps remaining stored data
Delete permanently
- Default
- Confirmed action on rejected data
- Options
- Delete / Cancel
- Meaning
- Irreversible inside app
Delete all rejected
- Default
- Confirmed action
- Options
- Delete rejected set
- Meaning
- Check backup first
How it works
Disposition (Normal/Rejected), activity (Race/Practice/Unknown) and completion (Live/Completed/Incomplete) are separate concepts. Reject is a user organisation choice. Permanent deletion removes the Session and its owned stored detail and cannot be undone inside LapMind.
Limitations
The active live Session is telemetry-owned and not an ordinary editable/deletable historical record. An orphaned live record may need MARK INCOMPLETE before removal. Deletion does not remove independent files already exported elsewhere.