Repository navigation
[FEATURE]: Exactly Once Approval #398
Description
Activity
- added a parent issue
on Jul 22, 2026 This might have a tie in with header forwarding - I've noted as such but the issues will likely be worked on in paralell
{{ message }}
Summary
Current gating for HITL will not guarantee the handing of the approval in an atomic manner. This ticket adds strong mapping between the approval service with a proper mutex to ensure the approval is only handled once. Subsequent approvals could cause task forking depending on the application or lead to unexpected behavior. Strong addressable storage into the #329 backend is the proper storage place.
Additional Context
No response
Upload screenshots
No response
Searched Issues
Code of Conduct