> ## Documentation Index > Fetch the complete documentation index at: https://qodex.ai/docs/llms.txt > Use this file to discover all available pages before exploring further. # Missions > Use Qodex missions to keep API catalogs, scenarios, and product-quality checks moving without starting from a blank chat each time. # Missions Missions are repeatable Qodex jobs for work that should happen more than once. Use a mission when you want Qodex to keep a product area healthy over time, such as syncing an API catalog, creating missing scenario coverage, reviewing newly changed routes, or checking whether existing scenarios still match the app. ## What a mission contains Each mission has: * **Goal**: the outcome Qodex should work toward. * **Instructions**: project-specific rules, constraints, and preferences. * **Parameters**: the collection, environment, tags, branches, or product area the mission should use. * **Run history**: every run, its status, and the work Qodex completed. * **Impact stats**: the visible changes created by the mission, such as endpoints synced, scenarios proposed, or checks completed. The mission card shows enough context to decide whether to run it, pause it, or inspect the latest result. ## Start from a preset Mission presets give you a guided starting point. A preset fills in the common goal and asks only for the details Qodex needs for your project. Common presets include: | Preset | Use it when | | ----------------- | -------------------------------------------------------------------------- | | Collection sync | Your API has changed and the catalog should reflect the latest endpoints. | | Scenario coverage | A product area has important paths with little or no test coverage. | | Regression upkeep | Existing scenarios need to stay aligned with the current product behavior. | | PR follow-up | A merged change should lead to updated catalog rows, scenarios, or checks. | You can edit the goal and instructions before saving the mission. ## Run now Click **Run now** when you want a mission to run immediately. This is useful after importing a new collection, merging an API change, changing auth settings, or finishing a product area that needs fresh coverage. Scheduled missions can still run on their cadence. A manual run simply starts the mission without waiting for the next schedule. ## Collection sync Collection sync is the mission most teams start with. On the first run, Qodex can perform a full sync so the catalog has a clean baseline. Later runs focus on what changed, keeping the endpoint catalog useful without forcing you to re-import and reconcile everything by hand. When sync finds new or changed endpoints, review the catalog rows, open important requests in the [API Playground](/docs/api-testing-playground), and promote stable requests into [API scenarios](/docs/api-testing-scenarios). ## Review before promotion Missions are designed to help Qodex do the repetitive work while keeping you in control of what becomes active. When a mission proposes scenarios, catalog changes, or follow-up work, review the result before relying on it in schedules, CI, or merge gates. Keep drafts as drafts until the request shape, auth profile, assertions, and environment are correct. ## Where missions fit Missions do not replace scenarios or test runs. They help create and maintain them. * Use [scenarios](/docs/concepts-scenarios) for reusable test logic. * Use [test runs](/docs/run-tests) to execute scenarios and review results. * Use [endpoint catalog](/docs/api-testing-endpoint-catalog) to understand API coverage. * Use missions when Qodex should repeatedly keep those assets up to date. ## Related See the API map that collection-sync missions keep current. Turn synced requests into reusable tests. Run the scenarios that missions help maintain. Give missions stable product context and testing rules.