- Purpose
- Prevent the recurring failure modes seen in enterprise rollouts.
- Prerequisites
- A scenario that runs end to end in the sandbox
- Architecture
- Checklist applies to the integration layer, not to Integration Lab configuration alone.
Configuration
| Owner | Solution Engineer + customer technical lead |
Implementation steps
- 01External identifier is immutable and unique.
- 02Every write carries an idempotency key.
- 03Retries use exponential backoff and a dead-letter queue.
- 04Revocation path implemented for refund, cancellation and offboarding.
- 05Webhook signatures verified and replay window enforced.
- 06Secrets stored server-side and rotatable.
- 07Audit log captures request id, actor, outcome for every call.
- 08Runbook exists for the top three failure modes.
Testing procedure
- Replay every event twice
- Simulate a 5xx from Integration Lab and confirm no data loss
Troubleshooting
Go-live slips on security review
Bring the security section of this lab to the first technical call, not the last.