> 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/crm-automation/activities-of-flows/activity-limit.md). # Activity: Limit The **Limit** activity lets only a set number of players pass a step of the flow. The first players, up to the limit, go to the **Matched** branch; everyone after them goes to **Not Matched**. The **Limit** activity is available in the flow builder of both Journeys and Scheduled Campaigns. {% hint style="info" %} Important: the activity limits progress, not per user, but globally. In other words, you cannot use this activity to ensure that a specific user passes through it only X times. It acts as a global limit, meaning only the first X attempts will succeed, regardless of whether the user is the same or all the attempts were from different users. To restrict how many times an individual player can enter a campaign rather than applying a global cap, configure the campaign's entry mode settings (such as *Once during open journey* or *Once in a lifetime*) or use profile state checks. {% endhint %}

The Limit activity in the Flow control group of the palette

Limit activity on the canvas — 1 — the live counter on the activity; 2 — its branches: Matched and Not Matched

The counter counts only the players sent to **Matched**. A player goes to **Matched** while the count is not above the limit: with a limit of 100, players 1 to 100 go to **Matched**, and player 101 and later go to **Not Matched**. Players sent to **Not Matched** are not counted, so the counter stops at the limit. The default **Entry limit** is 100 and can be set to any positive whole number. **Here's an example scenario:** *You can set up a journey to award bonuses to players who have made deposits of 100 EUR or more, with only the first 30 players who enter the campaign receiving the bonus.* On the canvas, the Limit activity shows a live counter, **Entry limit: X / Y**: X is the number of players sent to **Matched** so far, and Y is the limit. Players are counted in the order in which they reach the Limit activity. The counter on the canvas can be up to about a minute behind, and it shows a new value when you open or reload the flow.

Example: the campaign starts on a deposit of 100 EUR or more

Example: only the first 30 players get the bonus

### Limit Activity Reset You can choose whether the progress of the **Limit** activity is reset. The option is available for: * Daily campaigns * On specific Days of the Week campaigns * On specific Days of the Month campaigns * Journeys **For scheduled campaigns** — the switch **Reset limit on next scheduled run** is off by default, so the progress is not reset when the campaign runs again. When it is on, the progress is reset each time the campaign runs again, while the limit itself stays the same.

Limit settings in a scheduled campaign — 1 — the reset switch of a scheduled campaign

**For Journeys** — the switch **Reset limit** is off by default, so the progress is never reset. When it is on, choose a **Schedule**, and the progress is reset on that schedule, while the limit itself stays the same. The **Schedule** has three options: * **Daily** — every N days at a set time; * **Days of week** — on the days you pick, at a set time; * **On a specific date & time** — once, at that moment. All Journey reset schedules use UTC: set the hour and minute in UTC. Click **See next runs** to check the next reset times. A reset can happen up to a minute after the set time.

Limit settings in a journey: 1 — Entry limit; 2 — Reset limit; 3 — the reset Schedule

### Outgoing connections The Limit step can have these outgoing connections:

| # | Connection | When the player goes this way | | - | --------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | | 1 | **Then** | Right away, when Smartico starts the step. It does not wait for the result, so it also runs when the step fails later. | | 2 | **Matched** | The counter was still below the limit: the player is let through. The step stays open. | | 3 | **Not Matched** | The limit was already reached: the player goes this way instead, and the step is closed. With nothing connected here, the player has no next step. | --- # 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/crm-automation/activities-of-flows/activity-limit.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.