Activity Log & replay
The Activity Log is where you see exactly what AutoSync is doing — every event it receives and every action it takes — and where you fix things when a sync fails. It's a troubleshooting tool, not a reporting dashboard.
Two views
- Booking Activity (default) — booking events with directional labels ("MB → GHL Create Appointment"), the class/appointment name, calendar, status, and a Replay button.
- Webhook Activity — every inbound event, with the outbound API calls it triggered nested beneath as child rows. Failed parents auto-expand.
Reading status
| Status | Meaning |
|---|---|
| Success | Processed cleanly. |
| Partial | Succeeded partly — e.g. the booking was recorded but the contact sync was skipped. |
| Skipped | Intentionally not processed — no calendar mapping, a duplicate, or auto-create is off. |
| Failed | Errored — the Error Response column names the cause. See Errors. |
| Processing | In the queue, not finished yet. |
Use Hide Config Errors to filter out setup-related noise (no calendar set, calendar disabled) while you focus on real failures.
Contact detail
Click any contact to drill in:
- Event Timeline — the same log, filtered to just this contact.
- Field State — every synced field with its current value on each system, when it last synced, and an in-sync dot. This is the "show me the truth across all systems" view.
Fetch live platform values makes a real-time call to Mindbody / Booker, checks off any fields that differ, and lets you push the corrected values to HighLevel with Save to CRM.
Replay a failed sync
Fixed the underlying config? Click the circular Replay arrow on a failed outbound action to re-run it. A few rules:
- Only failed outbound actions can be replayed (inbound webhooks must be re-sent from the platform).
- Replay uses diagnostic data kept 30 days on success, 90 days on failure — after that the button is disabled.
- The account must be Active, and replays are limited to 10 per minute.
Last updated July 2026