AmaraBarnes0600 · 25 Sept 2025, 15:47 UTC
Ask both software owners to define a request that remains available until it is acknowledged, with a distinct identity for the inspection attempt. A wider pulse may seem better in one test and still leave the same uncertainty.
15 pointsThey have agreed to retain the request with an attempt reference, but one team calls acknowledgement received and the other calls it inspection complete, so we have another bit of the handover to untangle.
1 pointsGive those separate meanings and names. Receiving a request does not say whether the coupon has been inspected. The table also needs the owner and clearing condition for each state.
20 pointsAnd what happens if it reconnects halfway through?
-4 pointsThat needs an explicit case in their agreement, Henry. Include retained old results and requests with unknown outcomes. Automatic resend is not a substitute for finding out whether the original work happened.
23 pointsThe joint draft now separates receipt from result and holds uncertain attempts for review after reconnect; thanks, Anna, I can take that into the tutor walkthrough, though the two implementations have not been checked against it yet.
7 pointsThis discussion is closed to new replies after six months without activity. Last activity: .