Two staff members can approve the same request at nearly the same time. Resolve the decision once in trusted state and keep execution singular, rather than treating each approval event as a new action.
Duplicate decisions and quorum rules differ
A duplicate approval repeats a decision for one proposal under a single-reviewer policy. A quorum workflow intentionally requires several distinct approvals. The data model must distinguish these cases rather than infer the policy from how many people clicked.
For a proposed single-decision workflow, use an atomic transition from pending to approved or denied. Record the winning current decision and the disposition of later requests. Execution receives one logical operation identity independent of approval-delivery count.
If policy requires multiple approvers, represent the required roles and distinct decisions explicitly. Two clicks by one person should not satisfy a two-person requirement unless that unusual rule is deliberately authorised.
Reproduce a fictional simultaneous approval
Two managers open the same address-correction proposal. Both approve before seeing the other’s response. The system records one accepted authorisation and returns the existing state to the second manager. Only one customer update is eligible to execute.
Add a conflicting race where one manager denies while the other approves. The approved business policy must determine resolution through a singular trusted transition or an explicit conflict state, not whichever asynchronous worker happens to run last.
| Concurrent fixture | Required invariant |
|---|---|
| Two approvals, one-decision policy | One logical authorisation |
| Approval and denial together | Deterministic documented resolution |
| Duplicate browser submission | Existing decision returned safely |
| Required two-person review | Distinct authorised decisions checked |
| Two execution workers | One effect under the operation contract |
Test simultaneous requests with a controlled barrier. Sequential clicks cannot establish concurrency safety, even if both return a friendly message.
Preserve who acted without confusing state
Audit all attempted decisions with safe identities and their dispositions. Staff should see whether their click changed state or encountered an already decided request. Do not rewrite history to imply both independently authorised separate operations.
Atomic decision storage does not guarantee exactly one external effect after a lost response. The executor still needs duplicate protection and reconciliation. Keep decision concurrency and side-effect uncertainty as complementary controls.
This workflow is proposed. The voice integration case study describes related backend experience. Pair it with parallel action prevention.
Concurrent approval FAQ
Should every approval click create a job?
No. Jobs should follow the one current logical authorisation under the defined policy.
Can two managers satisfy a quorum automatically?
Only when their distinct roles and decisions meet the explicitly configured requirement.
What proves the design works?
Concurrent decision tests plus destination-side assertions show whether one intended business effect occurred.