A multi-agent finance workflow can draft vendor payments but must not execute transfers above a threshold without controller approval. Edge cases include missing invoices and conflicting vendor bank details. How should you implement human-in-the-loop?
Select an answer to reveal the explanation.
Short Explanation
You need human-in-the-loop that pauses only high-risk payments for controller approval while routine steps keep running. Use approval workflows, human overrides, and edge-case handling so missing invoices or conflicting bank details don't slip through.
Full Explanation
Implement approval workflows, human overrides, and edge-case handling so high-risk actions pause for controllers while routine steps continue automatically. Use targeted checkpoints, not all-or-nothing automation. Encode thresholds in orchestration so the payment execution tool is unreachable without an approved token or state. Give controllers a concise packet—amount, vendor, evidence—rather than raw chain-of-thought, and support reject/edit paths that feed back into agents. Persist human-in-the-loop state durably so long approval delays do not lose workflow context. Gate only sensitive tools/actions and resume the graph after decisions. Auto-approving every payment path violates control requirements. Requiring a human to retype the entire conversation for every step overuses humans. Silently dropping payments creates silent financial risk.