Recover from broken links, loading errors or an interrupted app
Who and before: Any customer; protect unsaved drafts and downloaded private records.
Start: The page's error/retry screen or ordinary navigation.
Steps:
1. Read the message and identify the intended account and action. If safe, use Retry/Back or reopen the record from My Activity.
2. For an emailed link, use the original latest relevant message. Sign in as the intended recipient; do not paste its private token into chat.
3. For a payment/action timeout, first check its record before retrying a consequential submission.
4. Before reload, logout, clearing data or reinstalling, preserve unsynced text/photos and verify any account-saved draft.
5. Contact support with the page, device and non-sensitive reference if recovery fails.
Result and check: The correct record loads or a clear unresolved error remains.
Limits and recovery: Refresh cannot restore every expired/consumed link, device draft or provider state. A not-found page may mean a removed listing, old alias or unauthorized context. Do not guess developer/debug routes, reset storage reflexively or create duplicate accounts.
Start: The page's error/retry screen or ordinary navigation.
Steps:
1. Read the message and identify the intended account and action. If safe, use Retry/Back or reopen the record from My Activity.
2. For an emailed link, use the original latest relevant message. Sign in as the intended recipient; do not paste its private token into chat.
3. For a payment/action timeout, first check its record before retrying a consequential submission.
4. Before reload, logout, clearing data or reinstalling, preserve unsynced text/photos and verify any account-saved draft.
5. Contact support with the page, device and non-sensitive reference if recovery fails.
Result and check: The correct record loads or a clear unresolved error remains.
Limits and recovery: Refresh cannot restore every expired/consumed link, device draft or provider state. A not-found page may mean a removed listing, old alias or unauthorized context. Do not guess developer/debug routes, reset storage reflexively or create duplicate accounts.