> 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/calendar-troubleshooter.md).

# Availability preview

Use **Preview availability** from availability settings to inspect how a user’s calendar, working hours, and meeting timing affect available slots.

<figure><img src="https://2442454418-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQA3GQNrIYVrPQ90NBwRa%2Fuploads%2FbluWbjpEhRMQWbayOYwR%2FCleanShot%202026-09-10%20at%2021.13.29%402x.png?alt=media&amp;token=9a370a51-e34b-41d9-9282-8f3c65154f6f" alt=""><figcaption></figcaption></figure>

1. Select an **Event type**.
2. Choose an **Availability schedule**: **User working hours** or a team schedule.
3. Select the **Calendar user** whose connected calendar you want to check.
4. Click **Preview availability**.

Use **Week**, **Day**, or **4 days** to inspect the calendar. **Schedule details** shows the duration, buffers, start-time intervals, and schedule timezone.

Admins can select other workspace members with a primary connected calendar. Members can inspect their own calendar.

This preview uses the user or team schedule you select. Check the actual link or router when diagnosing custom weekly hours, event dates, group participants, or routing eligibility. See [Unavailable times](/settings/find-unavailable-times.md) for the other checks that can affect booking.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.distro.so/settings/calendar-troubleshooter.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.