> For the complete documentation index, see [llms.txt](https://help.sesami.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sesami.co/get-started/onboarding/troubleshooting/session-expired.md).

# Session Expired

“Session expired” or “invalid link” can happen when booking links are opened after they expire or when cookies are blocked.

## Common causes

* Link opened much later (expired session)
* Browser blocks third-party cookies
* Aggressive privacy extensions
* Cached storefront pages serving outdated session data

## What to try

{% stepper %}
{% step %}

#### Open in incognito/private window

Try opening the booking link in a browser private or incognito window.
{% endstep %}

{% step %}

#### Disable ad blockers/privacy extensions temporarily

Some extensions can block cookies or scripts required for the booking session.
{% endstep %}

{% step %}

#### Clear browser cache and cookies

Clearing cache and cookies can remove outdated session data that causes the link to be treated as expired.
{% endstep %}

{% step %}

#### If on mobile, try another browser

Try opening the link in Chrome or Safari (or a different mobile browser) to rule out browser-specific cookie or privacy settings.
{% endstep %}
{% endstepper %}

## If the issue is frequent

* Review your theme caching setup
* Ensure the booking entry point is using the current embed/block

Related:

* Safari cookie issues: **/troubleshooting/safari-cookies**


---

# 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.sesami.co/get-started/onboarding/troubleshooting/session-expired.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.
