AgentforceAdvancedidempotencypaymentsreliability
Design agent actions for idempotent financial transactions
Real World Scenario
Network retries caused duplicate loyalty point credits when customers asked the agent to apply a promotion twice.
Expected Answer
• Accept idempotency keys on write actions stored with unique constraint
• Return same success response on duplicate key within TTL window
• Agent prompt instructs confirming amount before final credit action
• Transaction log object linking conversation ID to financial operations
• Reconciliation batch detecting duplicate credits by key or pattern
• Compensating actions for identified duplicates with audit trail
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Accept idempotency keys on write actions stored with unique constraint Also consider: Return same success response on duplicate key within TTL window In practice: Agent prompt instructs confirming amount before final credit action Optimize for scale and operational observability.
Architect Perspective
Agents retry more than humans—every financial write action needs idempotency by design.