> 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-missions.md).

# Recurring Missions

**Recurring missions** work similarly to **generally available missions -** players can start progressing immediately without needing to meet any unlock conditions.

You can define a **recurrence schedule** for the mission in **Recurrence of mission**:

* **Hourly**
* **Daily**
* **Days of week** (specific days of the week)
* **Days of month** (specific days of the month, or the last day of the month)
* **A few times: On specific dates and time**

In **Runs** you set the time of each reset and, except for **A few times**, its time zone (UTC by default). With **A few times: On specific dates and time**, if no End date or **Time to Complete the mission** is set, the mission stays available for 30 days after its last scheduled run. After that, it moves to the Missed tab if it is not completed.

Once the mission becomes visible in the gamification widget, players can make progress. At the end of each recurrence period, the mission progress is **automatically reset** for all users based on the defined schedule.

{% hint style="success" %}

* After activation, the mission will **only appear in the UI** once the **next reset date** (as defined in the recurrence schedule) is reached. Until then, it will remain hidden.
* **Recurring missions** can be configured with an **opt-in requirement**, meaning players must actively join to participate. Regardless of opt-in status, **all progress resets** at the end of each recurrence period. Players will need to **opt in again** when the mission becomes available for the next cycle.
  {% endhint %}

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-b12ccabef12b276580655aa8f0c93850f72675d8%2FScreenshot_4.png?alt=media&amp;token=9ecffca8-70a3-421d-965e-a82a6564d5c3" alt=""><figcaption><p>BO: 1 — Recurrence of mission, 2 — the days the mission resets (Runs), 3 — the time zone of the reset</p></figcaption></figure>

### Activity period: Weekdays and Days of the month

Recurring missions use the **Activity period** setting instead of the Availability period. You find it in the mission form under **Additional**, and it works the same way as the Activity period in Campaigns. It decides when the mission is visible to players, open for opt-in and counting progress. It does not change when progress resets; that is still set by **Recurrence of mission**.

| Option                     | What you set                                                     | Mission is active                                             |
| -------------------------- | ---------------------------------------------------------------- | ------------------------------------------------------------- |
| **Not set** (default)      | Nothing                                                          | Always, following the recurrence schedule only                |
| **Time period + Weekdays** | Optional Start and End date, plus one or more weekdays           | Between the Start and End date, on the selected weekdays only |
| **Days of month**          | One or more days (1–31), or **last** for the last day of a month | On the selected days of every month                           |

Missions that already had a Start or End date open with **Time period + Weekdays** selected and their dates kept. The Start and End date behavior described further down this page (the "Availability Period" cases) applies to these dates.

![BO: Activity period in a Recurring mission set to Time period + Weekdays, Saturday and Sunday](https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FBfmmv17EMHWf8GV5PjLM%2Fperiod-in-missions-91426d0f-948529.png?alt=media)

**How the mission behaves for players**

| Area               | On an active day                                               | Outside the active days                                                                                                 |
| ------------------ | -------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Visibility         | Shown under Available, or In progress if the player has joined | Hidden. With **Show mission before Start date** set to Yes, shown under Locked with a countdown until the mission opens |
| Opt-in             | Allowed                                                        | Not allowed                                                                                                             |
| Progress           | Qualifying events count as usual                               | Events don't count, even for players who already opted in                                                               |
| Completed missions | Stay visible under Completed                                   | Stay visible under Completed                                                                                            |

On each reset set in **Recurrence of mission**, progress goes back to zero and opt-ins expire. When the next active day starts, players see a fresh mission and, if opt-in is required, opt in again.

**Related settings**

* **Time to complete the mission** is disabled and cleared once weekdays or days of the month are selected. The mission runs until its next recurrence.
* **Show mission before Start date** is available for Recurring missions once an Activity period type other than **Not set** is selected. It controls whether the mission shows as Locked with a countdown on inactive days.
* **Require explicit opt-in** works as before. Opt-ins never carry over to the next cycle: players opt in again in every recurrence cycle. There is no separate switch for this on Recurring missions.
* **Cloning** a mission copies the selected weekdays or days of the month. Start and End dates are not copied.
* Changes to weekdays and days of the month are recorded in the mission's change history.

**Example: weekend-only mission with mandatory opt-in**

* **Recurrence of mission:** weekly, Saturday 00:00 UTC
* **Activity period:** Time period + Weekdays, Saturday and Sunday
* **Time to complete the mission:** empty (cleared automatically)
* **Opt-in:** Require explicit opt-in set to Yes (players opt in again every cycle)

Players see the mission from Saturday 00:00 to Sunday 23:59 UTC and must opt in each weekend. From Monday the mission is hidden, or shown as Locked with a countdown if **Show mission before Start date** is on. The reset can also run mid-week; players still only see and progress the mission on the weekend.

To have a daily mission on weekend days only, set **Recurrence of mission** to Saturday and Sunday at 00:00 UTC and the Activity period to the same days. The mission then starts from zero on each weekend day.

To run a mission on specific days of the month, for example the 1st and the 15th, select **Days of month** with those days and set the recurrence to the same days. Use **last** for a mission on the last day of each month.

{% hint style="info" %}

* Active days are whole calendar days in **UTC** (00:00–23:59 UTC). The player's timezone is not used, and there is no time-of-day window within a day.
* **Days of month** clears the Start and End date and the weekdays. **Time period + Weekdays** clears the days of the month. Only one type applies at a time.
* **last** is selected on its own, not together with other days. Day 31 is only active in months that have 31 days; use **last** to cover every month.
* An event counts by the time it happened, not the time it was processed. A bet placed on Sunday at 23:58 UTC still counts for a weekend mission if it is processed after midnight.
  {% endhint %}

{% hint style="info" %}
In the cases below, the mission is shown under the Locked tab before its Start date only when **Show mission before Start date** is set to Yes. With No, the mission stays hidden until the Start date. Timers that count to the End date stop at the next reset if it comes first.
{% endhint %}

<mark style="color:blue;">**\[Opt-in: OFF]**</mark>**&#x20;Recurring mission + Availability Period**

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 (only if the mission already occurred and is visible, otherwise will remain hidden until start date) 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 (or until the next reset, if it comes first).
* **When the End date is reached,** the mission will go to the Missed tab with the ‘Expired’ chip. There will be no timer, and the mission will not recur again.

<mark style="color:blue;">**\[Opt-in: OFF]**</mark>**&#x20;Recurring mission + Time to complete the mission**

If the opt-in option is disabled and 'Time to complete the mission' is set, the mission will have the following behavior:

* **Once the mission becomes available** (the Reset date is reached), the mission is displayed under the Available tab with a timer showing the time left to complete the mission.
* **When the ‘Time to complete the mission’** is reached and the mission is not completed, it will go to the missed tab with a timer showing the time until the next reset date (Until the mission will be available again).

<figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fgit-blob-fdb522cdd70620b7c227357ca0594b0302df9dd3%2FScreenshot_59.png?alt=media&amp;token=35fde26f-bbad-4d83-8361-7c4bb8893710" alt=""><figcaption></figcaption></figure>

<mark style="color:blue;">**\[Opt-in: OFF]**</mark>**&#x20;Recurring mission + Time to complete the mission + Availability Period**

If the opt-in option is disabled, 'Time to complete the mission' is set, and 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 (only if the mission already occurred and is visible, otherwise will remain hidden until start date) 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 that is set in the ‘Time to complete the mission’ setting. This timer takes into consideration the End date as well, and it shows the shortest period that is left. So, in case the End date is closer in time than the time set in Time to complete the mission, the timer will show the time left until the End date and vice versa.
* **When the time to complete the mission is reached** and if the mission is not completed, it will go to the Missed tab with a timer showing the time until the next reset date.
  * If the End date is before the Reset date, there will be no timer, since the mission will not recur after the End date is reached.
* **When the End date is reached** and the mission is not completed, the mission will go to the Missed tab with the ‘Expired’ chip. There will be no timer, and the mission will not recur again.

<mark style="color:purple;">**\[Opt-in ON]**</mark>**&#x20;Recurring mission + Availability Period**

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 (only if the mission already occurred and is visible, otherwise will remain hidden until start date) 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 left until the End date is reached (or until the next reset, if it comes first), an active Opt-in button, and 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 user has opted in or not, if the mission is not completed, it will go to the Missed tab with the ‘Expired’ chip. There will be no timer, and the mission will not recur again.

<mark style="color:purple;">**\[Opt-in ON]**</mark>**&#x20;Recurring mission + Time to complete the mission**

If the opt-in option is enabled and the 'Time to complete the mission' is set, the mission will have the following behavior:

* **Once the mission is visible on the UI**, the mission is displayed under the Available tab, there is an active Opt-in button, and a ‘Requires opt-in’ chip. The timer is showing the time until the next reset date.
* **After Opt-in,** the timer is changed, and it shows the time left to complete the mission with the ‘You are opted in’ chip.
* **When ‘The time to complete the mission’ is reached**, the mission will go to the Missed tab with a timer showing the time left until the next reset date.

<mark style="color:purple;">**\[Opt-in ON]**</mark>**&#x20;Recurring mission + Time to complete the mission + Availability Period**

If the opt-in option is enabled, 'Time to complete the mission' is set, and Start and End dates are configured, the mission will have the following behavior:

* **Before the Start Date, t**he mission will appear under the Locked tab (only if the mission already occurred and is visible, otherwise will remain hidden until start date) with a label indicating the start date and a countdown timer showing the time remaining until it becomes available.
* **After the Start Date, t**he mission will move to the Available tab, with a timer showing the time that is left until the End date is reached and the Opt-in button. This timer takes into consideration the End date as well, and it shows the shortest period that is left. So, in case the End date is closer in time than the time set in Time to complete the mission, the timer will show the time left until the End date and vice versa.
* **After Opt-in,** the timer is changed, and it shows the time left to complete the mission with the ‘You are opted in’ chip.
* **When the ‘Time to complete the mission’ is reached** and the mission is not completed, it will go to the Missed tab with a timer showing the time until the next reset date.
  * If the End date is before the Reset date, there will be no timer, since the mission will not recur after the End date is reached.
* **When the End date is reached** and the mission is not completed, the mission will go to the Missed tab with the ‘Expired’ chip. There will be no timer, and the mission will not recur again.


---

# 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-missions.md?ask=<question>&goal=<user_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.
