> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/faq/faq-generale/ma-session-a-disparu-de-mon-planning-que-faire.md).

# My session has disappeared from my schedule, what should I do?

**Rest assured:** your sessions cannot disappear. Even after a mishandling, they remain in your schedule. If you no longer see them, it is almost always due to an active filter that is hiding them.

#### Filters: culprit number 1 of “disappearances”

The display of your sessions depends on the filters you have activated. For example:

* If you have the "hide unassigned sessions" filter enabled and drag a session to the *Unassigned* row, it will **instantly disappear from view on the next refresh**... but it will still be there, just hidden.
* Other filters can hide your sessions based on status, team, or activity type.

#### How to check?

1. At the top right of your schedule, click on the small **gear** to open the display settings.
2. Make sure the active filters match what you want to see.
3. Temporarily disable all filters to check if your session reappears.

#### Trick

If a session "disappears" right after dragging and dropping, immediately consider active filters before concluding that it has been deleted.


---

# 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.yoplanning.support/en/faq/faq-generale/ma-session-a-disparu-de-mon-planning-que-faire.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.