Domfolio Knowledge Library

Operations and Runbooks

Operational procedures for incident response, sync failures, and release safety.

Audience
On-call and operations teams
Source
docs/runbooks/README.md
Last updated
March 3, 2026

Operational Priorities

  • Keep auth and API pathways available for both web and mobile clients.
  • Detect integration sync failures quickly and provide replay tools.
  • Preserve auditability for security and financial operations.

Runbook Library

  1. API incident triage with request ID correlation and error envelope review.
  2. Token compromise response: revoke sessions, rotate secrets, audit impacted calls.
  3. Webhook failure response: validate signatures, inspect dedupe keys, replay safely.
  4. Sync backlog handling: prioritize failed outbox events and watch retry saturation.

Release Safety Checklist

  • Run targeted unit and API tests before merge.
  • Run affected Playwright flows for changed UX pathways.
  • Validate migrations and admin visibility for operational models.
  • Confirm feature flags and rollout guards are configured per environment.

Source File

Operational runbooks are tracked in docs/runbooks/README.md.