跨應用程式工作流程:相連步驟並不等於工作流程
Connected steps are not a workflow
跨越支援系統與帳單系統的退款流程顯示,單是串接 Agent 的操作步驟並非完整工作流程;若沒有核對系統間的規則與狀態交接,Agent 即使完成各應用程式允許的操作,仍可能出錯。退款低於五十美元、訂單已付款且從未退款時可處理,超過則由經理決定;向客戶發出訊息前,流程亦未確認退款已成功入帳。
Take a task that crosses two apps. A customer asks for a refund. The request lives in the support desk. The order lives in the billing system. End to end, the agent reads both, decides against the refund rules, issues the refund, and confirms back to the customer.
The rules are in neither API. Refunds under fifty dollars are fine when the order is paid and never refunded before. Over that, a manager decides. Testimonials wait for a human before they go live. Escalation happens after two contacts. None of that lives in the support desk or the billing system. It lives in the team's heads.
Now watch the handoffs. The agent reads the order in billing. Then it moves to the support desk carrying a snapshot of a moment that has already passed. Billing permits the refund under one permission set. The support desk writes the customer note under another. Nobody confirms the refund actually landed before the note goes out.
Connected steps are not a workflow. The agent did everything the apps allowed and still got it wrong, because the rules and the handoffs live in the gaps between the apps.
Where does your multi-app workflow recheck state before it acts.
AIAgents #AgenticAI #BuildInPublic #DevCommunity
來源:DEV Community · dev.to
