> For the complete documentation index, see [llms.txt](https://docs.bifrost.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bifrost.io/for-collators/stop-collating.md).
# Stop Collating
To stop collating and leave the candidate pool, you must first schedule a request to leave the pool. Scheduling a request does not automatically remove you from the candidate pool, you must wait an exit delay (84 rounds). After the delay you will be able to execute the request and stop collating. While you are waiting the specified number of rounds, you will still be eligible to produce blocks and earn rewards if you're in the active set.
#### Schedule Request to Leave Candidates
To get started and schedule a request, navigate to the **Developer** tab, click on **Extrinsics**, and take the following steps:
1. Select your candidate account
2. Select **parachainStaking** pallet under the **submit the following extrinsic** menu
3. Select the **scheduleLeaveCandidates** extrinsic
4. Enter the `candidateCount` which you should have retrieved in the [Get the Size of the Candidate Pool](/for-collators/run-a-collator.md#get-the-size-of-the-candidate-pool) section
5. Submit the transaction. Follow the wizard and sign the transaction using the password you set for the account
#### Execute Request to Leave Candidates
After the waiting period has passed, you'll be able to execute the request. To execute the request to leave the candidate pool, you'll first need to obtain the number of delegations the candidate has. To do so, you can query the candidate information, which will include the delegation count. To get started, click on the **Developer** tab, select **Chain state**, and take the following steps:
1. From the **selected state query** dropdown, choose **parachainStaking**
2. Select the **candidateInfo** extrinsic
3. Choose the candidate account to get the information for
4. Click the **+** button to submit the extrinsic
5. Copy the **`delegationCount`** to be used for executing the leave candidates request
{% hint style="danger" %}
Important Step: Check and wait until the number in round \`current\` larger than your candidate 'leaving' number, then you can execute the following step below, otherwise, it will fail.
{% endhint %}
Now that you have the delegation count you can execute the request. Switch back to the **Extrinsics** tab and follow these steps:
1. Select your candidate account
2. Select **parachainStaking** pallet under the **submit the following extrinsic** menu
3. Select the **executeLeaveCandidates** extrinsic
4. Select the target candidate account (anyone can execute the request after the exit delay has passed after submitting the `scheduleLeaveCandidates` extrinsic)
5. Enter the candidate's delegation count
6. Submit the transaction. Follow the wizard and sign the transaction using the password you set for the account
---
# 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.bifrost.io/for-collators/stop-collating.md?ask=&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.
