> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/settings/find-unavailable-times.md).

# Unavailable times

Start with the exact booking link and date the guest is trying to use. A free-looking calendar doesn't always mean the time can be booked.

| Check                | What can hide a time                                                                                                                                                   |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Timezone             | The guest, browser, and account may display the same moment differently.                                                                                               |
| Weekly hours         | The time falls outside the schedule used by this event type.                                                                                                           |
| Calendar connection  | A disconnected account prevents Distro from reliably checking availability.                                                                                            |
| Busy events          | An event on the calendar checked by this booking flow blocks the time. See [Calendars](/integrations/calendars.md) before relying on an additional connected calendar. |
| Event dates          | The event type only accepts bookings during its configured dates and hours.                                                                                            |
| Duration and buffers | The full meeting and required space around it don't fit.                                                                                                               |
| Minimum notice       | The proposed start is too soon.                                                                                                                                        |
| Booking window       | The date is too far in the future.                                                                                                                                     |
| Group participants   | Every required participant must be available together.                                                                                                                 |
| Routing              | The expected host may not be eligible under the router's current rules.                                                                                                |

In the Distro app, open **Settings → My Availability → Preview availability** to use the calendar troubleshooter.

<figure><img src="https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FXKbGA6w0aHcG0bvMOBJ5%2FCleanShot%202026-09-10%20at%2021.13.29%402x.png?alt=media&amp;token=b5a7012e-7b1a-4722-a9d8-5077cb40cb4a" alt=""><figcaption></figcaption></figure>

Check the link's selected event type before changing your weekly hours. An event type can use team hours, custom weekly hours, or specific event dates instead of your usual personal schedule.

If you change router configuration, [activate the updated version](/routing/router-versions.md) before testing a new routing attempt. Existing attempts can keep the version they started with.

Availability is checked again when a booking is confirmed. If a displayed time becomes unavailable, reload the current times and choose another slot.


---

# 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://help.distro.so/settings/find-unavailable-times.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.
