If your webhook isn't creating bookings, the webhook log is your first stop. Go to **Settings → Webhooks**, find your webhook card, and click **View Logs**.
The webhook was received and acknowledged, but CalendarPA didn't create a booking. This is intentional — ThriveCart won't see an error.
**Why it happens:**
- **Webhook is inactive** — Toggle the webhook active in CalendarPA
- **Product not in filter** — The purchased product's ID isn't in your Product Filter. Check your Product Filter setting, or clear it to accept all products
- **Wrong event type** — ThriveCart sent a refund, renewal, or other non-`order.success` event. Only purchases trigger scheduling
**Hover the log row** to see the exact reason.
The Signing Secret in CalendarPA doesn't match what ThriveCart is sending.
**Fix:**
1. In ThriveCart, go to **Settings → API & webhooks → ThriveCart order validation**
2. Copy the exact secret word
3. Update the Signing Secret in your CalendarPA webhook settings
Note: The secret is case-sensitive. Even an extra space will cause a mismatch.
CalendarPA received the request but couldn't parse the payload. The log shows a snippet of the raw body.
**Common causes:**
- Misconfigured ThriveCart webhook URL (wrong format)
- Non-ThriveCart requests sent to a ThriveCart webhook URL
- Payload format mismatch (ThriveCart supports both form-encoded and JSON)
Auto-book mode was used, but no capacity was available. CalendarPA sent a schedule link instead and sent you an alert.
**Fix:** Add more GROUP sessions or check if your 1-on-1 availability has any open slots.
1. **Check the URL** — Confirm the webhook URL in ThriveCart exactly matches the one shown on your CalendarPA webhook card
2. **Test the connection** — In ThriveCart, use the webhook test feature to send a sample request
3. **Check the webhook is active** — The toggle on the webhook card must be on
4. **Verify ThriveCart's delivery settings** — ThriveCart may have delivery retries disabled if an endpoint returns repeated errors
Use the Gleap chat button to contact support. Include your webhook log entries (screenshot or copy the status + timestamp) so the team can investigate quickly.