Troubleshooting guide
Double bookings require manual correction: A Practical Diagnostic Path
Double bookings require manual correction can have several causes that look identical from the outside. Use this path to gather useful evidence without making the original problem harder to reproduce.
Record the symptom before changing it
Capture the exact screen, user role, time, device, and sequence that produces the issue. Note whether appointment rules differ by service or staff member occurs at the same time.
- Save exact error text
- Record the last known working date
- List recent code, content, vendor, DNS, or account changes
Separate reachability, data, and behavior
First confirm whether the affected system can be reached. Then confirm the expected record or content exists. Only then test the behavior supported by constraint-aware scheduling logic.
- Reachability check for payment and deposit workflows
- Data or content check related to service and staff availability rules
- Behavior check for appointment durations, buffers, and capacity
Use stop conditions
Stop and preserve evidence if a test could overwrite data, invalidate logs, lock out users, or remove the only working copy. Recovery work needs a known restore path before intrusive changes.
- No confirmed backup
- Unknown production ownership
- Security or payment data may be involved
Verify the repair in the real journey
A green technical check is not enough. Repeat the original journey, test a nearby edge case, and confirm the result from the perspective of service businesses whose scheduling rules exceed a basic calendar embed.
- Service and staff availability rules
- Multi-location and resource scheduling
- Email and SMS notification hooks