> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/set-application-workflow-execution-order.md).
# Set Application Workflow Execution Order
By reordering your application workflows, you can control the sequence in which these workflows run.
When multiple workflows have overlapping conditions, their order can lead to different results. For example, a *reject partners outside the US* workflow and an *accept all creators* workflow could produce conflicting outcomes for a creator located outside the US. If the auto-accept workflow runs first, the application will be approved. If the auto-reject workflow runs first, it will be rejected.
1. From the left navigation menu, select  **\[Engage]** → **Partners** → **Automation** → **Workflows**.
2. From the Workflows screen, select the **Application** tab.
3. In the upper-right corner, select **Reorder Workflows**.
4. On the *Reorder Workflows* modal, use the drag-and-drop feature to reorder your workflows.
5. Select **Save**.
* Your application workflows should now execute based on the new sequence.
---
# 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.impact.com/brand/what-would-you-like-to-learn-about/platform-features/review-partner-applications/automate-partner-application-processing/set-application-workflow-execution-order.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.
