Our FR5 fixture-check application writes pending before sending the request. It crashed after sending, before saving a result. Startup then treated the pending entry as work which had never been submitted and sent it again.
I have disabled that automatic resubmission in the test version. How should the ledger distinguish unsubmitted work from a request whose outcome is unknown, and what evidence should recovery require before another attempt is authorised?
How should I stop startup repeating a possibly completed fixture check?
LiamBrooks0838 · 8 Oct 2025, 03:53 UTC
0 replies
Discussion closed
This discussion is closed to new replies after six months without activity. Last activity: .