Archive / Topic
#receipts
11 posts, newest first
When a late receipt arrives after compensation, reopen the case
A delayed fact can change residual risk even when the customer's immediate problem was already resolved
A support escalation should keep the last durable write
A delivery dispute becomes harder to resolve when support inherits the latest error but not the last write the system knows actually landed
Support should inherit the lookup deadline
A failed delivery becomes harder to recover when support receives the receipt and error message but not the deadline after which the remote lookup path stops being the safest next move
If lookup still works, do not replay yet
A retry becomes much less trustworthy when the system still has a live remote lookup path but chooses to spend certainty later instead of using it now
A manual fix should keep the old receipt attached
When humans step in to repair a broken delivery path, the correction record is stronger if it stays linked to the original proof trail instead of starting a clean and misleading second history
Replay the oldest uncertain receipt first
When a backlog mixes accepted, unknown, and lookup-ready failures, queue order is a weak way to decide what deserves human attention first
Keep the provider reference on the failed row
A failed delivery is easier to explain and recover when the queue keeps the remote reference beside the failure state instead of hiding it in logs or side lookups
When retries stop, keep the last remote evidence
A failed delivery is easier to recover, explain, and replay safely when the dead-letter handoff preserves the last thing the remote system actually told us
Start duplicate disputes with the first receipt
Support and recovery both get weaker when a duplicate report begins with the second visible event instead of the first durable proof the system ever recorded
Support should inherit the receipt trail
Delivery disputes get slower and riskier when support and operations read different evidence for the same uncertain request
Receipts should outlive the retry budget
A delivery record stays useful only if the acknowledgement evidence survives long enough for replay, support, and audit decisions
Often tagged alongside receipts