> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/products/gamification-basics/missions/recurring-upon-completion-missions.md). # Recurring upon Completion Missions The recurring upon completion missions reset and become available again immediately after completion. You can set a specific maximum number of completions or leave it unlimited: * **Unlimited completions:** If no limit is set, the mission will always reappear after it’s completed. Once completed for the first time, the mission will appear in both the 'Available' and 'Completed' tabs. * **Limited completions:** If you set a maximum number, the mission will reset after each completion until the limit is reached. After the first completion, the mission will appear in both the 'Available' and 'Completed' tabs. Once the completion limit is reached, it will only be shown in the 'Completed' tab and will no longer be accessible. {% hint style="info" %} In the Back-Office mission configuration (General tab), this limit is controlled by the **Max completion count** field. Leave this field blank for unlimited completions, or enter a number (up to 999,999) to cap how many times players can complete the mission. {% endhint %}

BO: Creation wizard in Missions

Key details about ‘Recurring upon completion’ missions: * **Opt-in available:** Players can choose to participate in these missions or not. You can decide whether players need to opt in after each recurrence of the mission or not. By default, players only need to opt in once - they’ll be automatically opted in in all future recurrences of the mission. If you enable the **'*****Require opt-in after every recurrence**’* option, then players will be required to opt in again each time the mission recurs. Note that actions performed between completing a cycle and opting in to the next cycle do not count retroactively. * **Set availability period:** You can define a start and end date for when the mission will be active. * **No reward claiming:** These missions do not include a separate reward claim process. * **Missions without an availability period:** If no Start or End Date is configured, the mission becomes available immediately upon activation and does not show a countdown timer in the player widget. It remains active continuously until the maximum completion limit is reached (or indefinitely if set to unlimited). * **No per-cycle time limit:** The "Time to Complete the mission" duration setting is disabled for this mission type. A recurrence cycle has no deadline and only resets when all required tasks are completed. **\[Opt-in: OFF]**** Recurring upon completion mission + Availability Period** {% hint style="info" %} The behavior described below applies when **“Show Mission Before Start Date”** is enabled (default). If this setting is disabled, the mission remains hidden until its Start Date is reached, after which it becomes available (visible) to players. {% endhint %} If the opt-in option is disabled and the Start and End dates are configured, the mission will have the following behavior: * **Before the Start Date,** the mission will appear under the Locked tab with a label indicating the start date and a countdown timer showing the time remaining until it becomes available. * **After the Start Date,** the mission will move to the Available tab, with a timer showing the time until the End date is reached. * **When the End date is reached** and the active recurrence is not completed, it moves to the Missed tab with an Expired chip. If the player has completed the mission before, it also shows under the Completed tab, where it appears only once, regardless of how many times the player has completed it. **\[Opt-in ON]**** Recurring upon completion mission + Availability Period** {% hint style="info" %} The behavior described below applies when **“Show Mission Before Start Date”** is enabled (default). If this setting is disabled, the mission remains hidden until its Start Date is reached, after which it becomes available (visible) to players. {% endhint %} If the opt-in option is enabled and the Start and End dates are configured, the mission will have the following behavior: * **Before the Start Date,** the mission will appear under the Locked tab with a label indicating the start date and a countdown timer showing the time remaining until it becomes available. There is a disabled ‘Opt-in’ button. * **After the Start Date,** the mission will move to the Available tab, with a timer showing the time until the End date is reached. The opt-in button is active, and there is a ‘Requires opt-in’ chip. * **After Opt-in,** the timer continues counting the time until the End date, and there is a ‘You are opted in’ chip. * **When the End date is reached,** no matter if the player has opted in or not, if the mission is not completed, it will go to the Missed tab with an Expired chip. --- # 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.smartico.ai/welcome/products/gamification-basics/missions/recurring-upon-completion-missions.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.