GitHub user wenjin272 added a comment to the discussion: Human-in-the-loop approval: pluggable approver (decision model first, human fallback) - design discussion for #1067
Thanks for the discussion. I don't have a concrete design yet, but I see using a Decision Model for automatic approval as one possible approval policy. I agree that the policy should be pluggable. To me, the main challenge is how to suspend an ongoing task and resume it when human feedback arrives. We should also support a timeout mechanism so the application can decide what to do when an approval request remains unanswered for too long. One initial idea is to introduce a new `InputEvent` type representing an approval response for a previous Agent Run. Instead of following the normal input-processing path, this event would locate and resume the suspended task associated with that key. It would need to identify the specific run and approval request, rather than relying on the key alone, and avoid being buffered behind the task it needs to resume. This is only a starting point. We would still need to define how suspension survives recovery, how approval responses and timeouts interact, and how duplicate or late responses are handled. The point raised above about external side effects is also relevant: resuming an approved task does not by itself prevent an external operation from being executed twice. GitHub link: https://github.com/apache/flink-agents/discussions/1304#discussioncomment-19345268 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
