Errors & troubleshooting
When an event fails, the Activity Log shows the reason in the Error Response column. Most errors fall into two buckets you can fix yourself — configuration (calendar or setup) and authorization (a connection needs re-authorizing).
Common errors and fixes
| Error | What to do |
|---|---|
| No calendar set | Map that appointment type or class to a HighLevel calendar in Calendar Sync. |
| Slot no longer available | HighLevel availability doesn’t match the platform — fix duration, capacity, and hours. See Calendar sync. |
| Calendar ID is invalid | The HighLevel calendar was deleted — re-map it. |
| Calendar is disabled | Re-enable the calendar in HighLevel. |
| Calendar has no team members | Assign team members in the HighLevel calendar settings. |
| No client ID found | Contact resolution failed — often a household conflict or missing email/phone. |
| Class/service not found | The booking referenced a class that no longer exists on the platform. |
| Client already booked | A booking conflict — first-write-wins was applied. |
| API key / authorization invalid | Re-authenticate the platform connection. |
| Rate limited / server error / network error | A temporary platform issue — AutoSync retries automatically. |
i
Temporary errors (rate limits, 5xx, network blips) retry on their own with backoff — up to five attempts. You only need to act on configuration, authorization, and contact-resolution errors.
"My customer says their data is wrong"
- Activity Log → search the contact → open Contact Detail → Field State tab.
- Find the field with an out-of-sync dot, then open the event that should have updated it.
- Expand it to see the inbound data, the outbound request, and the response.
- If it was a config problem you've since fixed, click Replay.
"Bookings aren't syncing"
- Activity Log → Booking Activity → filter Status = Failed.
- Look for a pattern — same calendar, same staff, same class?
- Read the Error Response and apply the fix from the table above.
- Check the Alerts page for a related configuration alert.
"Something seems generally broken"
- Check the Health Summary bar at the top of the Activity Log.
- Filter Status = Failed and look for an authorization or configuration alert — an expired HighLevel token or a Mindbody authorization will block sync until resolved.
- Pattern alerts flag an elevated failure rate automatically.
Last updated July 2026