Decide where the work belongs
Name the repeated action
Describe what a person does when status is unclear and what duplicate or missed work can result. Compare queued event, failed channel, and absent event. Keep operational retry detail separate from what a user needs to decide.
Compare status remedies
Set durable in-app state, concise status, retry action, fallback channel, support path, and no change beside one another. Consider uncertainty and user control. Prefer a status that says what is known and offers one safe next step.
Choose the first slice
Record event class, channel, owner, and the local retry boundary. Decide whether to change copy, history, retry visibility, or duplicate handling. Preserve successful and uncertain controls for comparison. Describe what local confirmation can establish.
What to carry forward
Prioritize retry visibility where unclear status causes repeated actions or hides a durable event. The decision should name event and channel uncertainty. If status is already honest and no user decision is blocked, queue a different delivery issue.
Technical background: Android developer documentation.
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