> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/faq/plan-recommendations.md). # Do Plan Recommendations Account for Previously Submitted Plans? Yes, Archera's Commitment Planner always takes into account all of a customer's active commitments, whether acquired through Archera or directly from the cloud provider. Recommended plans on the Commitment Planner page do account for previously submitted plans though users should generally wait until a pending plan is processed before re-reviewing the recommendations. ## Waiting for Plan Processing Generally, you'll want to wait for 24 hours after a plan has been executed so that their coverage is reflected in the AWS CUR (Cost / Usage Report) or Azure CUR. Actioning a new plan will not cause you to be overcommitted as we will just add any net new commitments from the new plan to the original plan, but it is easier to just wait until the default plans update according to the new coverage! ## Related Resources * [Could Archera Change or Impact My Application?](/help-center/faq/could-impact-application.md) * [Does Archera Offer Professional Services?](/help-center/faq/professional-services.md) * [How Do I Audit Archera?](/help-center/faq/audit.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://docs.archera.ai/help-center/faq/plan-recommendations.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.