Production launch checklist
Verify the complete workflow and its recovery paths before customers depend on it.
Account and credentials
Confirm the live account profile matches the workflow your application implements.
- Credentials are server-side, current, and redacted from logs.
- Owning account, feature access, billing, and test-versus-production behavior are confirmed.
- Notary routing, eligibility, dispatch trigger, and fallback policy are recorded.
- Invitation, reschedule, cancellation, and document-release policies are verified.
Complete every supported customer journey
Use a real acceptance test for each route your product offers, not only a schema check.
- Create and prepare
Valid session, correct documents, correct fields, and the intended preparation hold.
- Route and invite
Correct notary pool or assignment and correct participant notifications.
- Join and sign
Intended device and identity experience for every participant.
- Complete and retrieve
Final event, all required PDFs, and any certificate/audit artifacts.
Prove the receiver is reliable
Test the configured authentication, event schema, retries, and recovery.
- Reject a request with an invalid configured webhook secret.
- Durably accept before acknowledging.
- Deduplicate managed deliveries before side effects.
- Handle repeated legitimate events and unknown future event types.
- Recover from reordered events, delayed completion, and expired file links.
- Inspect delivery logs and assign an operational owner.
Test session changes and failures
Exercise the situations your customers can actually encounter.
| Scenario | Expected evidence |
|---|---|
| Invalid or expired key | Clear authentication recovery. |
| Notary unavailable or ineligible | User-facing status and escalation path. |
| Reschedule / cancel / expire | Correct state, notifications, and events. |
| Late document or merge lock | Predictable error and next action. |
| Partial upload | Reconciliation without duplicate attachments. |
| Ambiguous create timeout | No blind duplicate creation. |
Test time and volume boundaries
Verify UTC, served timezones, daylight-saving changes, and rescheduling through actual dispatch. Exercise expected file sizes and request bursts against approved limits. A database timestamp test alone does not validate a scheduled notary notification.
Make operations supportable
Document the identifiers, logs, dashboards, and owners needed to investigate a failed customer journey. Keep keys and personalized URLs out of incident records.
A release is ready when someone outside the integration team can complete its supported workflow and resolve expected failures using the documented procedure.