Session interruption and return-state review
Review what session expiry tells a customer about unfinished work
Show the interrupted task and the return state so an expiry message can be reviewed against the draft behavior your team actually intends.
- ✓Continue means several things
- ✓Draft handling is unstated
- ✓The timeout page loses task context
Make the draft question part of the evidence
Interruption with a starting point
Keep unfinished work visible enough to explain why the expiry message matters.
Draft claims checked by a person
Distinguish uncertainty about preservation from observed loss after returning.
An explicit return destination
Agree where the customer should land before asking engineering to change the dialog.
Start from an interrupted task
A customer returns to an unfinished expense form in your application and selects Save. A session-expired dialog appears, but its Continue button does not explain whether the draft will survive. Review the interruption where it happens, not just a standalone timeout page. Ask the product owner which draft behavior is intended before turning the customer's uncertainty into a proposed implementation change.
Capture a reproducible expiry state
Use a controlled test session with synthetic expense details and an approved way to stage expiry. Record the unfinished form, triggering action, dialog, and return route after test sign-in. Keep credentials and session values outside the captured area. Note the staging method, build, route, and draft state. If the expiry state is simulated, distinguish that from observing a naturally timed-out session.
Report the missing promise carefully
Capture with the supported browser extension or upload authorized media into Retick. Review AI candidate findings against the sequence and annotate the dialog's action and draft language. A concrete issue is Expiry dialog leaves draft preservation unclear. Do not call it data loss unless a follow-up inspection actually shows missing data. Human editing should remove unsupported storage explanations and identify who must decide the preservation rule.
Example acceptance criteria
The dialog should state that another sign-in is required and describe the approved handling of unfinished changes. Its primary action should identify the next step rather than imply an immediate save. After the controlled return, the app should reach the agreed destination and show the expected draft or a clear explanation of its absence. Verify this manually with synthetic values; wording alone cannot establish preservation.
Follow the interruption through the revised build
Use a review cycle to compare the initial dialog and return state with the revision. Repeat expiry from a read-only page, a form with changes, and a form without changes so the message remains appropriate. Download approved findings or create selected individual-media Trello cards. Retick cannot establish server session lifetime, cross-tab invalidation, or persistence guarantees from media. Those need separate technical checks, and it does not restore a lost draft for the customer's application.
Review expiry at the moment work is interrupted
Capture a controlled timeout and define the message and destination together.