Salon/docs/runbooks/booking_failures.md

Runbook: Booking Failures

Symptoms

• POST /api/bookings/ fails (400/500).
• Booking status update fails.
• Booking missing/incorrect in listing.

Impact

Customers cannot book; staff schedule integrity degrades; dependent flows break.

Quick Checks

• Validate payload: service, staff, start_time, end_time.
• Check logs for validation/integrity errors.
• Confirm staff availability + overlap expectations.
• If notifications expected, confirm provider config + notification rows.

Mitigation

1. Reproduce with known test data.
2. Inspect booking validation service and serializer permissions.
3. Confirm timezone assumptions for failing case.
4. If regression after deploy, roll back booking-related change.

Escalation

Share booking id, user id, timestamps, and failing payload/response with engineering.

References

• Booking logic: backend/apps/bookings/
• Notification logic: backend/apps/notifications/