Business Reconciliation
A mechanism for detecting discrepancies by periodically comparing internal system records against the actual state of external service providers, used to detect and correct duplicate or missing business operations.
Timeline (last 90 days)
Business-side reconciliation is the most reliable yet most easily overlooked line of defense: periodically compare the set the system believes has been sent with the set the provider has actually sent, and alert on any discrepancy.
Business reconciliation does not depend on the trace execution path, so it can catch duplicate side effects across runs and workers, at the cost of additional storage and scheduled tasks.
Irreversible tool calls should carry business idempotency keys, write intent logs before and after each execution, and periodically reconcile with external systems; traces are used for troubleshooting performance, while reconciliation is responsible for answering whether duplication occurred.
All Facts (3)
Business-side reconciliation is the most reliable yet most easily overlooked line of defense: periodically compare the set the system believes has been sent with the set the provider has actually sent, and alert on any discrepancy.
50%UnverifiedBusiness reconciliation does not depend on the trace execution path, so it can catch duplicate side effects across runs and workers, at the cost of additional storage and scheduled tasks.
50%UnverifiedIrreversible tool calls should carry business idempotency keys, write intent logs before and after each execution, and periodically reconcile with external systems; traces are used for troubleshooting performance, while reconciliation is responsible for answering whether duplication occurred.
50%