Check whether the outcome improved
Check first use
Open an account with no history and confirm heading, explanation, scope, and optional start action. Ensure the message does not claim the system is broken or imply a prior event was read.
Check caught-up and filtered
Review an account with history but no unread rows, then apply a filter that excludes all records. Confirm copy distinguishes caught-up from filtered and that reset or broaden actions restore the expected list.
Review unavailable history
Exercise a missing or unavailable history boundary if supported and confirm the message states the limit without inventing absence. Inspect direct URL, focus, narrow layout, and status. Leave unobserved storage or sync cases outside closure. Confirm the explanation remains truthful after a filter change.
What to carry forward
Verification passes when first-use, caught-up, filtered, and unavailable states have truthful copy and appropriate recovery. If one history or sync state is untested, document it. A polished empty view is not enough if its reason is wrong.
Technical background: W3C guidance.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow