> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/application-reference/campaigns/campaign-settings/optional-settings/schedule/schedule-plan.md).
# Schedule Plan
## Details
The schedule plan is the output of all rules configured for your campaign.
#### Time
When the email is scheduled to be sent.
#### Email
The Email address of the recipient (not supported for anonymous campaigns).
#### Scenario
The specific attack or awareness scenario associated with the email.
#### Processed
The status email; pending, sent, or error.
***
## Rebuild Plan
This button is necessary if any modifications are made to an existing rule. Rebuilding the schedule plan ensures that all changes are reflected accurately, updating the schedule to align with the new configurations.
{% hint style="info" %}
Rebuilding a plan will not send emails to already processed recipients, ensuring that modifications can be made to a rule without compromising the integrity of the campaign.
{% endhint %}
***
## FAQ
What is the best practice for adding rules and validating the Schedule Plan?
Start with a controlled or small recipient group to familiarize yourself with the rule outputs. Add only one rule at a time, then validate the Plan to ensure the emails will be sent according to your goals.
Once you are confident, simply adjust the rule by adding all additional recipient groups and rebuild the scheduling plan. This approach allows for careful testing and refinement before scaling up to the full campaign.
No emails are sent after the Schedule Rule is saved
* Did you start the campaign after setting the scheduler? Please note that configuring the scheduler alone won't initiate email delivery. The campaign needs to be explicitly started to begin sending emails. Ensure that you have activated the campaign after setting up the scheduler to initiate the mail delivery.
* Did you start the campaign after the Schedule Rule Start time? Schedule Rules can not be initiated if the start time is in the past.
* If you are using the scheduler to trigger smishing campaigns, make sure your license has enough credits and is not outdated. You can check your license status and credits in the [License tab](/application-reference/account-settings.md).
* Make sure your Lucy server [**time** & **time zone**](/application-reference/settings/advanced-system-settings/advanced-settings.md#date-time-settings) are both correct.
* Apply the latest patches by [updating your Lucy server to the latest version](/application-reference/support/update.md).
---
# 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://wiki.lucysecurity.com/application-reference/campaigns/campaign-settings/optional-settings/schedule/schedule-plan.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.
