Validation, undo, retry, fallback, destructive action review, and recovery paths.
Browse all problem familiesOpen an entry for its decision rule, states, implementation contract, and source trail.
Auditing destructive dialogs, action sheets, menu items, command palette actions, delete receipts, account cancellation flows, permission revocation, bulk actions, and high-impact execution reviews.
Autosave failed, stalled, expired, or became uncertain while users still have meaningful local work.
The action is destructive, irreversible, costly, security-sensitive, privacy-affecting, or externally visible.
Use this anti-pattern entry to audit products that ask for confirmation on many routine actions or use identical prompts for different levels of risk.
A conflict has been detected and a user must choose, merge, save-copy, skip, or commit a result.
A user has initiated a destructive command that can permanently remove, revoke, reset, deactivate, or cancel something valuable.
Auditing disabled primary actions, toolbar commands, menu items, toggles, form controls, checkout actions, invite flows, publish controls, exports, destructive actions, and workflow steps.
Form submission can produce one or more errors.
Users have unsaved or pending changes that cannot be recovered if they leave.
Use this anti-pattern entry to audit products that show Undo, Restore, Revert, or rollback controls without proving exact reversal.
A primary lookup, verification, upload, payment, search, device feature, online-only step, or channel can fail while the user still needs to finish.
A richer UI control, script, API, media layer, device capability, or third-party widget improves the task but is not essential to the outcome.
A pull request, merge request, rebase, merge, or branch update has source-code conflicts that require developer decisions.
A denied user can request access, switch accounts, ask an admin, join a group, or use a safe fallback to continue.
Users perform reversible sequences of edits and can undo too far.
Deleted objects remain recoverable after the user leaves the original workflow.
A load, save, submit, upload, export, sync, payment, or background request failed for a transient or uncertain reason.
An authenticated session can expire because of inactivity, overall lifetime, assurance policy, or reauthentication requirement.
A severe action affects repository, project, workspace, account, production, security, billing, or organization-wide scope.
The action is common and mistakes are likely.
A close, cancel, switch, or edit-mode exit would discard unsaved local changes.
Use this anti-pattern entry to audit forms, editors, imports, checkouts, onboarding flows, and configuration screens where validation can erase recoverable user work.
Users edit documents, files, pages, design files, records, configurations, or published content over time.
Try fewer words, clear the filter, or search across all pattern families.
Search all patterns