> For the complete documentation index, see [llms.txt](https://help.aphex.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.aphex.co/docs/aphex-help-fr/questions-frequemment-posees/faqs/why-are-the-successors-not-scheduling.md).

# Pourquoi les successeurs ne se planifient-ils pas ?

Les successeurs sont des tâches programmées après une autre tâche. Il existe რამდენიმე raisons pour lesquelles votre successeur peut ne pas être replanifié après une modification apportée à une tâche prédécesseure :

1. Le successeur est **Terminé**, ce qui signifie que les dates de la tâche ont été actualisées. Aucune modification de date ne peut être apportée aux tâches terminées.
2. Le successeur est **Promis** et vous n'êtes pas le propriétaire de la tâche, la personne assignée ou un administrateur.
3. La tâche que vous avez déplacée est **Planifié**, et le successeur est **Promis.**&#x20;


---

# 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.aphex.co/docs/aphex-help-fr/questions-frequemment-posees/faqs/why-are-the-successors-not-scheduling.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.
