> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/troubleshooting.md).

# Troubleshooting

Symptom, cause and fix for the problems that come up most in dCal: no times on your booking page, a link that shows Page not found, a calendar that will not connect or block times, bookings missing fr

Each section names the symptom, explains what causes it and tells you where to check. For "can I do this at all" questions, see the [FAQ](https://docs.dapta.ai/dcal/faq.md).

***

## Your booking page shows no times

**Symptom:** a guest opens your event and sees a message where the calendar should be, or a day with no times.

| What the guest sees                                                                                                                                  | Cause                                                                                                                                                                                                                                  | Fix                                                                                                                                                                                                                                                     |
| ---------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **No available times in this range.**                                                                                                                | Nothing is free in the days the page offers, up to 60 days ahead or the event's **Booking window (days)** when it is shorter: your hours are taken, busy in the calendars you check for conflicts, or too soon for the minimum notice. | Widen your **Weekly hours**, look for busy events in your calendars, lower the event's **Minimum notice**, or raise its **Booking window (days)**. Requests waiting for your confirmation hold their time too: confirm or decline them in **Bookings**. |
| **No times are available right now. Please check back soon.**                                                                                        | A setup problem the guest is not told about: the event's schedule is missing, the schedule has no hours, or a team event has no hosts.                                                                                                 | Find the exact reason with the steps below.                                                                                                                                                                                                             |
| **We can’t read this calendar right now. Try again in a moment.** After **Try again**: **We still can’t read this calendar. Try again in a minute.** | A calendar with **Check for conflicts** on could not be read, and dCal has no good read of it from the last 5 minutes. dCal hides every time rather than risk a double booking.                                                        | Open **Calendars** and run **Test**. See [A calendar shows Needs attention](#a-calendar-shows-needs-attention).                                                                                                                                         |
| **No times available on this day.**                                                                                                                  | That day is full, or outside your hours.                                                                                                                                                                                               | Nothing to fix. The **Next day with times** button jumps to the next day with free times.                                                                                                                                                               |
| No day after a certain date has times                                                                                                                | The event's **Booking window (days)** ends there: guests can book only that many days ahead.                                                                                                                                           | Raise it in the event, or empty it for no limit. Booking pages never show more than 60 days ahead.                                                                                                                                                      |
| **No bookable events yet.** (on your profile page)                                                                                                   | You have no visible personal event.                                                                                                                                                                                                    | Create an event, or switch **Visible on the booking page** back on for one in **Events**.                                                                                                                                                               |
| **Lots of people are booking right now. The times will show in a moment.**, or a **Busy for a moment** card                                          | dCal is getting many requests at once.                                                                                                                                                                                                 | Nothing: the page tries again by itself.                                                                                                                                                                                                                |

### Find the exact reason

The guest's message is generic on purpose. To see the real cause, open **Bookings**, click **+ New booking** and pick the event, with **From available slots** selected. dCal names the problem and links to the fix:

| The notice says                                            | Fix                                                                                                |
| ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
| **This event’s schedule is missing**                       | Click **Open event settings** and pick a schedule in **Bookable hours**.                           |
| **No working hours configured for this event’s schedule.** | Click **Open Availability** and add hours to that schedule.                                        |
| **You don’t have a schedule yet**                          | Click **Create default working hours** under the notice, or create a schedule in **Availability**. |
| **Couldn’t reach the connected calendar**                  | Click **Check Calendars** and fix the calendar there.                                              |

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-60c81599560c9b86c438e8c364271458270695f6%2Fdcal-troubleshooting-01-new-booking-notice.png?alt=media" alt="The New booking page with the event Intro call selected, From available slots on, and the notice No working hours configured for this event&#x27;s schedule, with an Open Availability link"><figcaption><p><strong>+ New booking</strong> tells you exactly why an event offers no times, and links to the fix.</p></figcaption></figure>

***

## Fewer times than you expected

**Symptom:** the page shows times, but not the ones you expected.

Check these on the event, then on its schedule:

* **Slot interval (min)** decides how far apart start times are. It follows duration while they match; a different interval you choose stays independent. Set it to 60 for start times on the hour.
* **Minimum notice**: no time sooner than the chosen notice is offered. A new event starts at **2 hours**.
* **Booking window (days)**: nothing later than this many days from today is offered. Empty means no limit, and the booking page shows at most 60 days ahead either way.
* **Buffer before (min)** and **Buffer after (min)**: a time is offered only if the meeting and its buffers are all free.
* **Your hours**: the whole meeting has to fit inside one range. With hours until 17:00, the last start of a 60-minute event is 16:00.
* **Bookable hours**: the event may use a saved schedule or custom event hours instead of the working hours you edited, with its own time zone.
* **Requests waiting for confirmation** hold their time until you confirm or decline them.
* **Team events**: **Round-robin** offers a time when any host is free in their own working hours, **Collective** only when every host is. Each host's times come from their own default schedule and calendars. On a round-robin event with **Distribution** set to **Equal distribution**, a host with 3 or more bookings more than the least-booked host offers no times until the others catch up.

See [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md).

***

## Times show in the wrong time zone

**Symptom:** a guest says your times are off by some hours.

**Cause:** your booking page opens in the time zone the guest's browser reports. When the browser reports UTC or a zone the page cannot use, the page opens in your time zone instead, the one under the event: "{zone}, the host's time". If the guest's device is set to the wrong time zone, the page shows times in that wrong zone.

**Fix:** the guest opens the time zone control next to the times and picks their zone; every time on the page moves at once. If your own times are wrong, check the time zone of the schedule in **Availability**, which is the zone your hours are counted in, and your own in **Settings** > **General** > **Timezone**, which your emails and your **Bookings** page use. See [Time zones](https://docs.dapta.ai/dcal/calendars-and-availability/time-zones.md).

***

## Your link shows Page not found

**Symptom:** the page says **Page not found** and **This page does not exist. Check the link with the person who shared it.**

| Cause                                                                                                      | Fix                                                                                                                                                     |
| ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The event is **Hidden**. A hidden event has no public page; only one-off invite links open it.             | Switch **Visible on the booking page** on in **Events**, or send the guest a [one-off invite link](https://docs.dapta.ai/dcal/events/one-off-links.md). |
| You changed your **Public handle** or the event's **Event link**. Links with the old ones do not redirect. | Copy the link again with **Copy link** on the event's row and share it again.                                                                           |
| The event was deleted.                                                                                     | Create it again. Its past bookings are kept.                                                                                                            |
| The link was retyped by hand.                                                                              | Always share links with **Copy link**. Handles and slugs must match exactly.                                                                            |

A link with an old account code, from before you set a [custom link](https://docs.dapta.ai/dcal/share/custom-link.md), keeps working and redirects to the new one. Older links that start with `app.dcal.ai` keep working too: they send guests to the same page on `book.dcal.ai`, with the same address and query.

If the guest instead sees **This invite link has already been used**, the one-off link was used once already. Create a new one in the event with **Create invite link**.

***

## Your calendar will not connect

**Symptom:** the **Connect a calendar** dialog does not finish.

| Message                                                                                                                        | Cause                                                                                          | Fix                                                                      |
| ------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ |
| **Your browser blocked the popup. Allow popups for this site and try again.**                                                  | A popup blocker.                                                                               | Allow popups for app.dcal.ai, then click **Connect a calendar** again.   |
| **No {provider} connection for {email} yet. Finish the popup window, then check again.**                                       | You clicked **I’ve finished connecting** before you finished in the popup.                     | Finish signing in and granting access in the popup, then click it again. |
| **Still no {provider} connection for {email}. If you signed in with a different account, start again and enter that address.** | You signed in to a different account in the popup than the one you typed in **Account email**. | Start again and type the address of the account you sign in with.        |
| **Could not start the connect flow. Please try again.** or **Could not check for the connection. Try again in a moment.**      | A temporary failure.                                                                           | Wait a moment and try again.                                             |
| The popup shows **Could not connect**                                                                                          | The connection failed inside the popup.                                                        | Close the popup and start again from **Calendars**.                      |

See [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md).

***

## A calendar shows Needs attention

**Symptom:** a calendar on the **Calendars** page shows **Needs attention**, or guests see **We can’t read this calendar right now**.

Click the pill to check again, then click **Test**. The test reads your busy events for the next 14 days and tells you what it found:

| Test result                                                                   | Meaning                                                       | Fix                                                                            |
| ----------------------------------------------------------------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------------------ |
| A green result that starts with **Working** and says conflict-checking is ON  | All good.                                                     | Nothing.                                                                       |
| A green result that starts with **Working** and says conflict-checking is OFF | The calendar works, but its busy times do not block bookings. | Tick **Check for conflicts** on that calendar.                                 |
| **Not connected**                                                             | The calendar is not linked.                                   | Click **Reconnect**.                                                           |
| **Could not reach your calendar**                                             | dCal's access to the calendar expired or was removed.         | Click **Reconnect** and sign in to the same account.                           |
| **Connected, but reading your events failed.**                                | The provider did not answer the read.                         | Run **Test** again in a few minutes. If it keeps failing, click **Reconnect**. |

Reconnecting the same account keeps the same row and its settings.

***

## Busy events in your calendar do not block times

**Symptom:** guests can book over a meeting that is in your calendar.

* **Check for conflicts** is off for that calendar. Tick it on the **Calendars** page.
* The event has its own list in **Calendars for this event**, and that calendar is not ticked under **Check for conflicts** there.
* The meeting is an all-day event. All-day events in Outlook / Microsoft 365 never block, and in Google Calendar they block only when shown as busy. Use a timed event, shown as busy.
* The meeting is in a calendar account you have not connected. Connect it with **Connect another**.

***

## Bookings do not appear in your calendar

**Symptom:** a booking is in dCal but not in Google Calendar or Outlook.

* **It is a request.** Nothing is written to your calendar until you confirm it.
* **No calendar receives new events.** The **Calendars** page says **No calendar is set to receive new events yet.** Choose **Add new events here** on one calendar.
* **The event writes somewhere else.** Check **Add events here** under **Calendars for this event** in the event, and the line **New events are added to** on the **Calendars** page.
* **It is a team booking.** Each assigned host gets the event in their own receiving calendar.
* **The calendar could not be reached when the booking was made.** dCal keeps retrying for up to 24 hours; an event it still could not write by then is not added later. Fix the connection (see [A calendar shows Needs attention](#a-calendar-shows-needs-attention)) and add that meeting to your calendar by hand.

### The online meeting link is missing

* The event's **Location** must be **Online meeting** (the list may show your meeting platform's name instead) or **Not specified**. **In person**, **Phone call** and **Custom** never get a link.
* A calendar must receive new events. Without one, the event editor warns that no meeting link can be created.
* On a team event, the link comes from a host's own calendar set to receive new events: the host the booking went to on round-robin, one of the booking's hosts on collective and fixed round-robin. The team event editor warns you when hosts have none; each of them turns on **Add new events here** in their own **Calendars**.
* The link is created right after the booking. The confirmation email waits a little for it and goes out without it if it is not ready. The guest still finds it on their manage page under **Join the meeting**, and reminders include it.
* On a request, the link is created when you confirm it.

***

## Emails do not arrive

**Symptom:** a guest, or you, did not get an email about a booking.

**For your guest:**

1. **Spam or promotions.** dCal emails come from **dCal**, `calendars@notifications-dapta.ai`. Ask the guest to look there and to allow the sender.
2. **The email is switched off.** In **Settings** > **Notifications**, check that the email's switch is on under **Attendee emails**, for example **Booking confirmed**. Only admins and owners can open that tab.
3. **The address was mistyped.** Your copy of the booking email shows the address the guest entered.
4. **It is a request.** The guest gets **Request received**, without a calendar invitation, and the confirmation only when you confirm.
5. **Reminders.** They are set per event, in its **Reminders** tab. A reminder whose time had already passed when the booking was made is skipped: a booking made 30 minutes ahead gets neither the 24-hour nor the 1-hour reminder.
6. **dCal's email to that address is refused.** When the mail service refuses an address, for example because it bounced before, dCal does not retry. If you have a calendar that receives your bookings, it sends the guest its own invitation instead. Ask the guest for another address.

**For you:**

1. **You are not the host of that booking.** Host emails go to the booking's host. A **Round-robin** team booking notifies only the assigned host; **Collective** and **Fixed round-robin** bookings notify every assigned host. Admins and owners do not get copies of their teammates' bookings.
2. **The email is switched off** under **Host emails** in **Settings** > **Notifications**, for example **New booking**.
3. **Spam.** Allow `calendars@notifications-dapta.ai`.

See [Who gets which email](https://docs.dapta.ai/dcal/emails/who-gets-which-email.md).

**A teammate never got an invitation:**

1. **Spam or promotions.** Ask your teammate to look there.
2. **Resend it.** In **Settings** > **Members**, click **Resend invite** on their row. dCal sends one invitation per teammate per minute, so wait a minute after the last one.
3. **The daily limit.** A workspace sends up to 50 invitation emails a day, new and resent together. If you see the limit message, try again tomorrow.
4. **The address.** Check the email on their row. If it is wrong, **Remove** the invitation and invite the right address. Your teammate must sign in with the address you invited.

See [Invite teammates](https://docs.dapta.ai/dcal/account/invite-teammates.md).

***

## A guest cannot reschedule or cancel

| What the guest sees                                                                     | Cause                                                                                          | Fix                                                                                                                              |
| --------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
| **This link is no longer active**                                                       | The booking was rescheduled after that email. Each reschedule creates a new link.              | Use the link in the most recent email about the booking.                                                                         |
| The confirmation email has no **Manage your booking** button                            | You confirmed a request. The guest's manage link is the one in the **Request received** email. | Ask the guest to use that email. If they lost it, cancel the booking in **Bookings** and book them again with **+ New booking**. |
| **This booking has already taken place.** or **This booking can no longer be changed.** | The meeting already started, or it was cancelled or declined.                                  | Nothing to change. The guest can book again on your booking page.                                                                |
| Only **Cancel this request**                                                            | The booking is still a request, and a request cannot be moved.                                 | The guest cancels and books another time, or you confirm it first.                                                               |
| **No open times in the next 3 weeks.**                                                  | The reschedule picker shows the next 3 weeks only.                                             | Free some time in the next 3 weeks, or the guest cancels and books a later time on your booking page.                            |
| **We cannot read the host’s calendar right now. Try again in a moment.**                | A calendar you check for conflicts could not be read. The guest can still cancel.              | The guest clicks **Try again** in a moment. Check **Calendars** with **Test**.                                                   |
| **This link no longer works. Open the most recent email about this booking.**           | The link is out of date.                                                                       | Use the link in the most recent email about the booking.                                                                         |

See [Reschedule and cancel](https://docs.dapta.ai/dcal/bookings/reschedule-and-cancel.md).

***

## A guest sees an error when booking

| What the guest sees                                                                                          | Cause                                                                                                 | Fix                                                                                |
| ------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- |
| **You already have a booking**                                                                               | **One booking per person** is on for the event, and that email already has an upcoming booking on it. | The guest clicks **Use a different email**, or cancels the existing booking first. |
| **That time was just taken.**                                                                                | Someone else booked that time first.                                                                  | The guest clicks **Pick another time**.                                            |
| **Your hold expired**                                                                                        | The guest took more than 10 minutes to fill in the form.                                              | The guest clicks **Pick another time**.                                            |
| **We couldn’t confirm this time**                                                                            | A calendar you check for conflicts could not be read, so nothing was booked.                          | The guest tries again in a moment. Check **Calendars** with **Test**.              |
| **Lots of people are booking right now. Your details are still here: press Confirm again in a few seconds.** | dCal is getting many requests at once.                                                                | The guest presses **Confirm booking** again: what they typed is kept.              |
| **This invite link has already been used**                                                                   | The one-off link was already used.                                                                    | Send a new invite link.                                                            |

***

## An event will not save

One of these messages under a field means the event cannot be saved until you fix that field:

| Message                                                  | Field                                 | Fix                                                                                                                                |
| -------------------------------------------------------- | ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Use a whole number from 1 to 730, or leave it empty.** | **Booking window (days)**             | Type a whole number of days, or empty the field for no limit.                                                                      |
| **Use a full address that starts with https\://**        | **Redirect after booking**            | Type the whole address of your page, starting with `https://` and with no spaces. Addresses that start with `http://` are refused. |
| **Use the container ID, e.g. GTM-ABC1234.**              | **Google Tag Manager ID**             | Paste your container ID, the one that starts with `GTM-`.                                                                          |
| **Use the measurement ID, e.g. G-ABC123XYZ9.**           | **Google Analytics 4 measurement ID** | Paste your measurement ID, the one that starts with `G-`.                                                                          |
| **A Meta Pixel ID is numbers only.**                     | **Meta Pixel ID**                     | Paste the pixel's ID, digits only.                                                                                                 |
| **Use the project API key, which starts with phc\_.**    | **PostHog project key**               | Paste your PostHog project's API key, the one that starts with `phc_`.                                                             |
| **Choose PostHog US or EU cloud.**                       | **PostHog cloud**                     | Pick **US cloud** or **EU cloud**, the one your PostHog project lives in.                                                          |
| **A HubSpot portal ID is numbers only.**                 | **HubSpot tracking ID**               | Type your HubSpot portal ID, digits only.                                                                                          |

See [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md).

***

## Tracking tags or the thank-you page do not work

| Symptom                                                                                                                                                    | Cause                                                                                                                                                                                                                           | Fix                                                                                                                                                                             |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The event has no **Tracking and pixels** section                                                                                                           | Only owners and admins see it.                                                                                                                                                                                                  | Ask an owner or admin to add your tags.                                                                                                                                         |
| A tag sees no visits                                                                                                                                       | Tags load only on that event's own booking page: its event page, team event page or one-off link, embedded or not. They never load on your profile or team page, the guest's manage page, the studio preview or your dashboard. | Test with the event's own link. From a profile or team page, an event with tags loads as a full page, and its tags start there.                                                 |
| Google Tag Manager, Google Analytics or HubSpot get nothing from your embedded page                                                                        | Your embed code was copied before booking pages moved to `book.dcal.ai`. Those three tags do not run on the older `app.dcal.ai` frame; Meta Pixel and PostHog still do.                                                         | Copy the embed code again and replace the old one on your site.                                                                                                                 |
| **Google Tag Manager, Google Analytics and HubSpot can run code set up in your own account, so this deployment does not offer them on booking pages yet.** | You use a copy of dCal you host yourself, and its booking pages have no address of their own.                                                                                                                                   | Give booking pages their own address (`PUBLIC_BOOKING_URL`). Meta Pixel and PostHog work without it. See [Self-hosting](https://docs.dapta.ai/dcal/developers/self-hosting.md). |
| The guest sees **Taking you to {site}.** and **Continue** instead of your page                                                                             | The booking page is embedded on your site, and the browser did not let it move the whole page.                                                                                                                                  | The guest clicks **Continue**. Nothing to fix.                                                                                                                                  |
| A guest who reschedules or cancels is not sent to your page                                                                                                | Only a new booking redirects. Rescheduling or cancelling never does.                                                                                                                                                            | Nothing to fix.                                                                                                                                                                 |
| Your thank-you page gets no booking details                                                                                                                | **Booking details on that page** is set to **None: the address as you typed it**, the default.                                                                                                                                  | Choose **The event, its time and the campaign (UTMs)** in the event.                                                                                                            |
| Your thank-you page gets the event but not the booking's UTMs                                                                                              | The address in **Redirect after booking** already has a `utm_` parameter. Parameters already in your address win, so none of the booking's UTMs are added.                                                                      | Remove the `utm_` parameters from that address.                                                                                                                                 |

See [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md).

***

## A webhook is not received

**Symptom:** your endpoint does not get a booking event.

Check in **API and webhooks** > **Webhooks**, in the left menu:

1. **Is the webhook active?** A paused webhook drops its deliveries; they are not sent later.
2. **Does it listen to that event?** A new webhook starts with **Booking created** (`booking.created`) ticked. It gets **Booking rescheduled** (`booking.rescheduled`) and **Booking cancelled** (`booking.cancelled`) only if you ticked them too. The list does not show a webhook's events. To change them, delete the webhook and add it again, and give your endpoint the new signing secret. A declined request arrives as `booking.cancelled`.
3. **Click Ping.** dCal sends a signed test event and shows the result under the row.
4. **Open Deliveries.** It lists real deliveries, newest first. Pings are not listed there.

| You see                                                                                              | Meaning                                                                                                                                                                                                | Fix                                                                    |
| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------- |
| Ping: **Delivered** with a 2xx status, for example **Delivered (200)**                               | Your endpoint accepts deliveries.                                                                                                                                                                      | Nothing.                                                               |
| Ping: **Failed**, or `HTTP` and a status in **Deliveries**                                           | Your endpoint answered, but not with a 2xx. Only a 2xx counts as delivered, and a redirect (3xx) counts as a failure. Ping does not show the status code; **Deliveries** shows it for real deliveries. | Fix your endpoint, and use the final address, not one that redirects.  |
| `URL blocked at egress`, or Ping: **URL is not allowed.**                                            | The address points to a private or internal network.                                                                                                                                                   | Use a public `https://` address. Tunnel a local server while you test. |
| Ping: **Subscriber unreachable.**, or a connection error in **Deliveries**                           | Your endpoint could not be reached, or did not answer within 10 seconds.                                                                                                                               | Make it reachable, answer at once and do the slow work afterwards.     |
| `delivery could not be signed`, or Ping: **Cannot sign: the signing secret could not be decrypted.** | dCal could not use the webhook's signing secret.                                                                                                                                                       | Write to <support@daptatech.com>.                                      |
| Adding the webhook fails with **Subscriber URL rejected**                                            | The address is not `https://`, does not resolve, or points to a private network.                                                                                                                       | Use a public `https://` address.                                       |
| **No deliveries yet**                                                                                | No real booking event has happened since you added it.                                                                                                                                                 | Make a test booking on your booking page.                              |
| A line that starts with `Gave up after`, in **Deliveries**                                           | dCal retried that delivery for 24 hours without a 2xx answer, then stopped.                                                                                                                            | Fix your endpoint, then catch up with the REST API booking list.       |

The Ping results and these delivery messages are in English only.

dCal keeps retrying a failed delivery for up to 24 hours, waiting longer each time, and lists each try in **Deliveries**. Then dCal stops, that delivery is not sent again, and **Deliveries** shows a line that starts with `Gave up after`, the newest in the list at that moment. Keep your endpoint reliable, and if you missed events, catch up with the [REST API](https://docs.dapta.ai/dcal/developers/rest-api.md) booking list.

> **💡 Tip:** Process each delivery idempotently, keyed on its `X-Slate-Delivery` header: the same event can arrive more than once. If your signature check fails, see [Verify the signature](https://docs.dapta.ai/dcal/integrations/webhooks/verify-signature.md).

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-a95ae85af7dfc9e79cec370a66b76f191ed84fb3%2Fdcal-troubleshooting-03-webhook-deliveries.png?alt=media" alt="The Webhooks section with the webhook https://example.com/webhooks/dcal and its Deliveries list open: every row is a failed booking.created delivery with HTTP 405, newest first"><figcaption><p><strong>Deliveries</strong> shows each real delivery and what your endpoint answered.</p></figcaption></figure>

***

## HubSpot is not updating

**Symptom:** a booking is in dCal but no contact or meeting shows up in HubSpot.

Start with the HubSpot card in **Settings** > **Integrations**:

| The card shows                                                             | Cause                                                                                                                                              | Fix                                                                                                                                                                  |
| -------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Not connected**                                                          | Nobody connected HubSpot for this workspace.                                                                                                       | An admin or owner clicks **Connect**.                                                                                                                                |
| **Needs attention** with a list of missing scopes                          | The private app lacks a scope, usually `crm.objects.contacts.write`. A token without it still connects, and the first accepted booking then fails. | Grant the listed scopes to the private app in HubSpot. The token stays saved and the next accepted booking goes through on its own; there is nothing to paste again. |
| **Needs attention** with HubSpot's own error message and no list of scopes | HubSpot refused the token.                                                                                                                         | Check that the private app is still active in HubSpot. If you deleted it or its token, click **Disconnect** and connect a new token.                                 |
| **Disconnected**                                                           | Someone disconnected HubSpot.                                                                                                                      | Click **Reconnect**. Meetings already in HubSpot keep updating if you reconnect the same portal.                                                                     |

When you connect, **HubSpot rejected that token. Check that the private app is active and has both scopes.** means the token is wrong or lacks a scope, and **We could not reach HubSpot to check that token. Try again in a moment.** is a temporary failure. In both cases nothing was saved.

If the card shows **Connected**, check these:

* **The booking is a request.** Only accepted bookings reach HubSpot. A request is sent when you confirm it.
* **You are looking for an extra guest.** Only the person who booked becomes a contact.
* **The contact's name did not change.** dCal writes the name only when it creates a contact. A contact HubSpot already knows keeps its name.
* **A mapped answer is missing.** A blank answer never erases a value in HubSpot. Choice answers that match none of the property's options are dropped: the mapping shows which ones under **These will not be sent**. Mapped answers are written when a booking is accepted, not when it is rescheduled or cancelled.
* **A property is missing from the list.** dCal never creates properties. Create it in HubSpot, then click **Refresh properties**. **This property is no longer in your portal.** means it was deleted or archived in HubSpot.
* **The meeting has no owner.** dCal does not set the HubSpot owner. The host's name is in the meeting's description.

See [HubSpot](https://docs.dapta.ai/dcal/integrations/hubspot.md).

***

## Your embed does not show or looks wrong

| Symptom                                                              | Cause                                                                                                                                                             | Fix                                                                                                                                                                                                                                           |
| -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The frame shows **Page not found**                                   | The embedded event is hidden, or its handle or slug changed.                                                                                                      | Embed a visible event and copy the code again.                                                                                                                                                                                                |
| The frame stays tall or cuts the page                                | The code's `embed.js` script is missing or blocked.                                                                                                               | Paste the whole code, script included. Without the script the booking page still works, at a fixed minimum height.                                                                                                                            |
| Nothing appears                                                      | Your website builder removed the code, or your site's security policy blocks frames or scripts from other websites.                                               | Use your builder's HTML or embed block. If your site sets a Content-Security-Policy, allow `https://book.dcal.ai` for frames and scripts, and `https://app.dcal.ai` too if your code was copied before booking pages moved to `book.dcal.ai`. |
| The wrong language                                                   | Embedded pages follow each visitor's browser language.                                                                                                            | Add `lang=es` or `lang=en` to the address in the code, after `embed=1`, joined with `&`. It works on every embedded page.                                                                                                                     |
| **Manage your booking** opens a new tab                              | The guest's manage page cannot show inside another website.                                                                                                       | Nothing to fix.                                                                                                                                                                                                                               |
| The "Made with dCal.ai by Dapta" badge shows                         | Your workspace shows the Dapta branding.                                                                                                                          | Hiding it comes with a Dapta AI subscription. See [The Dapta badge](https://docs.dapta.ai/dcal/design/dapta-branding.md).                                                                                                                     |
| Your page stops reacting to bookings after you copied the code again | New code sends its messages, such as `dapta-calendars.booking_scheduled`, from `https://book.dcal.ai`. Code copied earlier sends them from `https://app.dcal.ai`. | If your page checks where a message comes from, accept `https://book.dcal.ai`, or both addresses.                                                                                                                                             |
| Bookings made on your embedded page have no UTMs                     | The code's `embed.js` script is not on your page, so the booking cannot read your page's address.                                                                 | Paste the whole code, script included.                                                                                                                                                                                                        |

See [Embed on your website](https://docs.dapta.ai/dcal/share/embed.md).

***

## You cannot open a settings tab or change a team

**You don’t have access** with **This section is available to workspace admins and owners.** means the page is for admins and owners only: the **Notifications**, **Members** and **Integrations** tabs of **Settings**, **Connect your agent**, **Tools**, and the pages under **API and webhooks**. Members do not see those three items in the left menu at all. Ask an admin or owner, or ask one of them to change your role in **Settings** > **Members**.

Creating, changing and deleting teams and team events also needs an admin or owner.

* Adding someone to a team fails with **No account member with that email**: the person must be in the workspace first. Click **Invite them from Members settings**.
* Deleting a team fails with **Delete the team’s event types first.**: delete the team's events, then the team. This message shows in English in both languages.

See [Members and roles](https://docs.dapta.ai/dcal/account/members-and-roles.md).

***

## The Create your first event screen keeps coming back

**Symptom:** every time you open the dashboard, dCal sends you to **Create your first event**.

**Cause:** you have no visible personal event, for example after you hid or deleted your only one. Team events do not count. **Skip for now** hides the screen only until you close the browser.

**Fix:** pick a template and click **Create event and finish**, or switch **Visible on the booking page** back on for one of your events.

***

## The branding switch or the custom link stays locked

**Symptom:** the **Dapta branding** switch shows **Included with your Dapta AI subscription**, or the studio shows **Custom links are included with your Dapta AI subscription.**, although your company pays for Dapta AI.

* dCal recognizes the subscription through the email address of the workspace's owner. Make sure the owner of the dCal workspace is the person who owns the Dapta AI subscription, then open **Settings** again. dCal keeps the last answer for up to 6 hours, so the switch can take that long to unlock.
* Only owners and admins can change these settings.
* **Your Dapta AI subscription ended, the branding is showing again** means the subscription lapsed. Renewing it restores your choice on its own.

If it still looks wrong, write to <support@daptatech.com>.

***

## Signing in fails

| What you see                                           | Fix                                                                                                                                                                                                                                                                                                                                            |
| ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Something went wrong signing in. Please try again.** | Click **Continue with Dapta** again and finish signing in within 10 minutes, in the same browser where you started.                                                                                                                                                                                                                            |
| **We couldn’t renew your session**                     | You are still signed in: the sign-in service did not answer. Wait a moment and click **Try again**.                                                                                                                                                                                                                                            |
| You land in the wrong account                          | Signing in always opens your own workspace. If the one you want is a workspace you joined by invitation, pick it in the workspace switcher at the top of the left menu. To use another Dapta account, click your profile button at the bottom of the left menu, then **Sign out**. Click **Continue with Dapta** and choose the right account. |
| **This invitation isn’t for this account**             | You opened an invitation while signed in with a different address. Click **Sign in with another email** and sign in with the address the invitation was sent to, or ask whoever invited you to invite the address you use. See [Invite teammates](https://docs.dapta.ai/dcal/account/invite-teammates.md).                                     |

***

## Your AI agent cannot connect or sign in

**Symptom:** Claude, ChatGPT or another AI agent cannot connect to dCal, or its calls to dCal fail. The agent usually repeats dCal's message, in English.

| What the agent reports                                                                                                  | Cause                                                                                                                                                                                                                                                                                                                                                               | Fix                                                                                                                                                                                                                                                                                                                        |
| ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **This sign-in is not an owner or admin of any account on this server yet.**                                            | You signed in, but you are not an active owner or admin of a dCal workspace, or you have not opened dCal on the web in that workspace within the last 30 days. The agent still connects, but only booking on public booking links works. An agent that worked before stops with this message once 30 days pass without a visit, or when your admin role is removed. | Open [app.dcal.ai](https://app.dcal.ai) in your browser and sign in with the same account (sign in again if it is already open), then ask the agent again. There is no need to reconnect. If it still fails, ask an owner to check your role in **Settings** > **Members**: a member asks an owner for the **Admin** role. |
| **This sign-in reaches several accounts, so the call must say which one.**                                              | You are an owner or admin in more than one dCal workspace.                                                                                                                                                                                                                                                                                                          | Tell the agent which workspace to use. See [If you belong to several workspaces](https://docs.dapta.ai/dcal/account/workspaces.md#if-you-belong-to-several-workspaces).                                                                                                                                                    |
| **Invalid, expired or revoked API key.**                                                                                | The agent uses an API key that was revoked, has expired or was copied wrong.                                                                                                                                                                                                                                                                                        | In **API and webhooks** > **API keys**, check the key's row (**revoked**, **Expired**). Create a new key and set it where the agent reads it.                                                                                                                                                                              |
| A message that says the API key **lacks scope**                                                                         | The key does not have the access that tool needs.                                                                                                                                                                                                                                                                                                                   | Create a key that includes it. A key's access cannot be changed after it is created.                                                                                                                                                                                                                                       |
| `Structured content does not match the tool's output schema: data/invitee_supplied must NOT have additional properties` | The chat loaded dCal's tools before an update added a field to `get_booking`. The agent checks every answer against the tool list it loaded, and that older list refuses fields it does not name. Tool lists loaded now accept fields added later.                                                                                                                  | Start a new chat, or reconnect dCal in the agent, so it loads the tools again.                                                                                                                                                                                                                                             |

To disconnect an agent you signed in, remove the dCal connector in that app. See [Connect Claude or ChatGPT by signing in](https://docs.dapta.ai/dcal/developers/connect-with-sign-in.md) and [API keys](https://docs.dapta.ai/dcal/developers/api-keys.md).

***

## Where each thing is checked

| Problem                             | Where to look                                                                                                                      |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| No times, or fewer than expected    | **Bookings** > **+ New booking** for the exact reason; the event's timing fields; **Availability**                                 |
| Wrong time zone                     | The zone in the guest's time zone control; the schedule's time zone in **Availability**; **Settings** > **General** > **Timezone** |
| Link shows Page not found           | The event's **Visible on the booking page** switch and **Copy link** in **Events**                                                 |
| Calendar connection or busy times   | **Calendars**: the health pill, **Test**, **Check for conflicts** and **Add new events here**                                      |
| Bookings missing from your calendar | **Calendars** and **Calendars for this event** in the event                                                                        |
| Emails                              | **Settings** > **Notifications**, and each event's **Reminders**                                                                   |
| Guest cannot reschedule             | The guest's most recent email; **Bookings**                                                                                        |
| Webhooks                            | **API and webhooks** > **Webhooks**: **Ping** and **Deliveries**                                                                   |
| HubSpot                             | **Settings** > **Integrations**, and **Send answers to your CRM** in the event                                                     |
| Embed                               | The embed code on your site, and **Embed on your site** in **Events**                                                              |
| Tracking tags or the thank-you page | The event's **Tracking and pixels**, **Redirect after booking** and **Booking details on that page**                               |
| Access                              | **Settings** > **Members**                                                                                                         |
| An AI agent connection              | Your role in **Settings** > **Members**; the key's row in **API and webhooks** > **API keys**                                      |
| Premium extras                      | **Settings** > **General** and **Settings** > **Booking Page**                                                                     |

## The event editor will not save

Read the error summary at the top. Click a listed field to open its tab and focus it; tab badges show how many fields need attention. For custom hours, keep at least one range, put the end after the start and remove overlaps on the same day. Add a detail for In person, Phone call or Custom locations. Fix unsupported calendar-text variables before saving. See [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md).

## Related

* [FAQ](https://docs.dapta.ai/dcal/faq.md): the questions hosts ask before they hit a problem.
* [How open times are calculated](https://docs.dapta.ai/dcal/calendars-and-availability/how-open-times-work.md): every rule behind the times on your page.
* [Connect your calendar](https://docs.dapta.ai/dcal/calendars-and-availability/connect-a-calendar.md): connecting, testing and reconnecting calendars.
* [Length, location and timing](https://docs.dapta.ai/dcal/events/event-settings.md): the booking window, the redirect after booking and tracking tags.
* [Webhooks](https://docs.dapta.ai/dcal/integrations/webhooks.md): how deliveries are made and retried.
* [Security and privacy](https://docs.dapta.ai/dcal/security-and-privacy.md): what is stored and how to delete it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dapta.ai/dcal/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
