Troubleshoot Yo Booking 2.0.2

Work from the failing layer in order: configuration, availability, appointment conflict, customer authorization, payment or notification service, integration delivery, then infrastructure.

Open the feature

Go to Yo Booking.

Before you start

• Record the service, staff, customer state, date, timezone, appointment ID, payment method, and exact error.
• Avoid testing destructive cleanup or restore on production.

Recommended workflow

1. Confirm version 2.0.0, schema status, required tables, and scheduled tasks.
2. Verify active service, staff assignment, business/staff hours, exceptions, lead time, and booking window.
3. Check existing appointments for conflicts.
4. Verify guest or signed-in authorization and self-service deadline.
5. Compare payment snapshot and ledger entries.
6. Review notification or webhook Delivery logs and retry only after fixing the cause.
7. Run one bounded end-to-end test before reopening live bookings.

What success looks like

• The failure is isolated to a specific configuration or service layer.
• A single representative booking completes without conflict and produces the expected payment, email, audit, and integration state.

Important notes

• Do not expose action tokens, API keys, webhook secrets, backup passwords, or customer data in support logs.
• Use the original upload/database backup when a maintenance action must be reversed.

Release and support resources

• View the product page
• Install the stable free version from WordPress.org
• Review the official release notes