---
title: Schedule a scenario
slug: schedule-a-scenario
description: Schedule your Make scenarios and set rate limits to control exactly when and how often they run
image: https://archbee-image-uploads.s3.amazonaws.com/oAyFj2GHlBeBVWF5OAir2/ZDfWtN_l9_C5xi_01XV7v_4.png
docTags: 
createdAt: 2025-02-03T13:29:15.599Z
---

Schedule a scenario to define when and how often your scenario runs.&#x20;

::embed[]{url="https://www.youtube.com/watch?v=r9jGFNT-eYE"}

## Schedule setting panel

Use **Schedule settings** to schedule your scenario. By default, a scenario runs every 15 minutes, but you can customize the run schedule and interval in this panel.

![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/JCe0glSHsrBFP8DTl7uR5-20260602-120827.png)

To find **Schedule settings**:

1. Go to the Scenario Builder.
2. Click **Every 15 minutes** on the Scenario toolbar.&#x20;
3. Configure your scenario schedule.

::Image[]{src="https://app.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/XYxUrx718klfibTyLfrA3-20251124-111825.png" size="48" width="444" height="463" position="center" darkWidth="444" darkHeight="463" showCaption="false"}

### Run a scenario&#x20;

You can select the following schedule options:

- At regular intervals
- Once
- Daily
- Weekdays (Mon-Fri)
- Weekly
- Monthly
- Specified dates
- On demand

When choosing any of these options, you may have to further define how often you want the run to occur. For example, if you select **At regular intervals,&#x20;**&#x79;ou must define the time interval (in minutes) between two consecutive scenario runs.&#x20;

You can add as many run times as you need in the **Daily** schedule, so one scenario can run at 1:00 AM, 14:40 PM, and 10:00 PM from one simple setup.

![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/Ga-g4PMqdvHZVxZ0jvDtD-20260512-081544.png)

The minimum length of the interval depends on your [plan](https://www.make.com/en/pricing).

The **Immediately** option is available only for some triggers. For more information on triggers, please see the [types of modules](docId\:PDoPIBceCKCboMPpKplmY) help guide.

:::hint{type="info"}
You can always see how much time is left until the next scenario execution on the organization dashboard.

![](https://api.archbee.com/api/optimize/PL8X94efBsjvhfQV3wyyj-kKSho7rG_I0OVVBM5cD-b-20250715-102621.png)
:::

### On-demand scheduling

With the on-demand scheduling option, your scenario waits for an API call or the **Run once** button to trigger it. The scenario does not have a schedule and it does not run unless you start it manually.

### Start and end date

To define the time range in which an activated scenario runs, check the **Show advanced settings** box and fill in the **Start** and **End** date.

## Set a scenario rate limit

Set a scenario rate limit to prevent scenarios with instant triggers from running too often in a short period. Without it, a scenario that runs tens of times per minute may exceed service rate limits and return errors. The default scenario rate limit is 100.&#x20;

To set a specific scenario rate limit for an instant trigger:

::::WorkflowBlock
:::WorkflowBlockItem
In the Scenario Builder, click **Immediately as data arrives&#x20;**&#x74;o ope&#x6E;**&#x20;Schedule settings.&#x20;**&#x20;
:::

:::WorkflowBlockItem
In **Maximum runs to start per minute**, specify a maximum number of scenario runs per minute or leave the field blank to have no limit. The default limit is 100.&#x20;

![](https://api.archbee.com/api/optimize/oAyFj2GHlBeBVWF5OAir2/9fNplGYjs6X5WwoXw8PUv-20260602-112056.png)
:::
::::

You've now set a scenario rate limit.

Once a scenario hits its maximum runs per minute, Make stores subsequent requests in a queue and processes them gradually as the limit allows. For example, if you set the maximum to 30 runs per minute, any additional requests queue until capacity is available.

:::hint{type="info"}
If your scenario includes a **Webhook response&#x20;**&#x6D;odule and exceeds the rate limit, the webhook caller receives an **HTTP 429 Too many requests&#x20;**&#x65;rror. This error means that the caller must wait and retry the request later.
:::

