GitHub user renezander030 added a comment to the discussion: Human-in-the-loop approval: pluggable approver (decision model first, human fallback) - design discussion for #1067
The narrower version makes one recovery case more common: if the job fails after an approved call has reached the ad platform but before its result is checkpointed, recovery replays the decision verdict and can send the same bid change a second time. I'd carry the pending-approval id into that call as its idempotency key and record the outcome as succeeded, failed or unknown next to the verdict, so recovery can tell an effect that already happened from one that never went out. I keep the consumed-action check in the same transaction as the dispatch record here: https://gist.github.com/renezander030/ad81c7a805a09a844983f881e2c487e5 GitHub link: https://github.com/apache/flink-agents/discussions/1304#discussioncomment-19176442 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
