A canceled chat stream leaves work running in three services. Define the user promise, reconcile actions already sent and test the race at the execution boundary.
Updated Nov 2026 · Original practice questions with worked answers and teaching rubrics. Our editorial policy explains the sources, review process and limits.
An outreach agent delegates twelve authorized appointment reminders to workers. In this fictional incident, the user presses Stop at 10:00:00 and the execution service records revocation at 10:00:01. The current UI says nothing was sent.
| Recipient service already confirms delivery | 3 |
|---|---|
| Dispatched, recipient service outcome unknown | 2 |
| Queued locally, not admitted for dispatch | 7 |
| Later event | At 10:00:04, the recipient service confirms both dispatched messages were delivered. |
| Provider capability | No message recall API. Workers may restart or receive delayed queue events. |
Your task. Define what Stop should guarantee, write the status shown during and after reconciliation, and specify how the execution boundary handles cancellation races and restarted workers.
A canceled chat stream leaves work running in three services. Define the user promise, reconcile actions already sent and test the race at the execution boundary.
This reference answer is in Premium. Free signup opens other answers.
9 answers per topic instead of 5, and your progress kept · no cardor unlock all 420 remaining answersNo comments yet. How would you have answered?