---
schema_version: "1"
id: 8c5179261205d8da1d49302f5bbd6d1a855c435ead1e5ed360f2ab8c7a06730f
title: Adding Schedules
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/api-functional-monitoring/afm-add-schedule.md
canonical_url: https://docs.mulesoft.com/api-functional-monitoring/afm-add-schedule
source_site: docs.mulesoft.com
content_type: documentation
content_hash: fd39610205e94ace71f1dcbaa73839671c34b1bd2258a9a6964a023c432ed20d
description: MuleSoft Documentation Site
latest: true
---
---
product: API Functional Monitoring
---

# Adding Schedules

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

You can add a schedule to an existing monitor if either of the following two conditions is true:

- You plan to run the test associated with the schedule in a public location, and the allocation of
  schedules for your Anypoint Platform organization is not exhausted.

- You plan to run the test associated with the schedule in a private location.

## Before You Begin

Ensure that you have the following permission set in Access Management:

- **Exchange > Exchange Administrator** or **Exchange > Exchange Contributor**

An Anypoint Platform administrator for your organization grants permission. See
[Manage Permissions](https://docs.mulesoft.com/access-management/managing-permissions).

## Add a Schedule

1.  Select the monitor in which you want to add a schedule.

2.  Click **Add Schedule** from the **Schedules** table.

3.  In the **Add Schedule** dialog box, select the following:

    - The location in which to run the test

    - The monitor schedule interval and its required information:

      <table><colgroup><col> <col> <col></colgroup><thead><tr><th>Interval</th><th>Required Information</th><th>Definition</th></tr></thead><tbody><tr><td><p>Hourly</p></td><td><p>The minute</p></td><td><p>The minute at which the test begins, starting 60 minutes after you create the schedule</p></td></tr><tr><td><p>Daily</p></td><td><p>The time of each day</p></td><td><p>The time each day (hour and minutes) at which the test begins</p></td></tr><tr><td><p>Weekly</p></td><td><p>Day of the week and time of day</p></td><td><p>The day of the week and the time of that day that initiates the test</p></td></tr><tr><td><p>Monthly</p></td><td><p>Day of the month and time of day</p></td><td><p>The day of the month and the time of that day that initiates the test</p></td></tr><tr><td><p>Advanced</p></td><td><p>Cron</p></td><td><p>The cron expression for the frequency of the test.</p></td></tr></tbody></table>

4.  Set **Configuration**.

5.  Click **Add**.

    The countdown to the first run of the selected test begins.

> [!NOTE] Specified test times correspond with your time zone.

## Limits for Schedule Intervals by Location

The minimum interval for schedules that run in private locations is always five minutes.

The minimum interval for schedules that run in public locations depends on the number of schedule
entitlements, or API monitor entitlements, that you have. If you have more than five, the limit is
five minutes. Otherwise, it is fifteen minutes.

The limit depends on the type of location, not on whether the API is public or private, because you
can test a public API from a private location.

<table><colgroup><col> <col> <col> <col></colgroup><thead><tr><th>Location Type</th><th>Number of Entitlements</th><th>Account Type</th><th>Interval Time Allowed</th></tr></thead><tbody><tr><td><p>Public</p></td><td><p>5 or less</p></td><td><p>Developer</p></td><td><p>15 minutes</p></td></tr><tr><td><p>Public</p></td><td><p>5 or less</p></td><td><p>Other</p></td><td><p>15 minutes</p></td></tr><tr><td><p>Public</p></td><td><p>More than 5</p></td><td><p>Developer</p></td><td><p>15 minutes</p></td></tr><tr><td><p>Public</p></td><td><p>More than 5</p></td><td><p>Other</p></td><td><p>5 minutes</p></td></tr><tr><td><p>Private</p></td><td><p>Any number</p></td><td><p>N/A</p></td><td><p>5 minutes</p></td></tr></tbody></table>

## Scheduling Long-Running Tests

Tests for a monitor that are run in public locations silently fail when the run time exceeds 120
seconds. If you need longer tests, the best solution is to use a private location, because you can
run tests that have a long duration in private locations.

If you want to run longer-running tests in a public location, you can:

1.  Download the monitor and split the tests across multiple monitors using the BAT CLI.

2.  Run and time each test to ensure that their running times are under 120 seconds.

3.  Upload the tests as separate monitors to run in the web UI or run them through BAT CLI.

## See Also

- [Differences in the Monitoring of Public and Private APIs](https://docs.mulesoft.com/api-functional-monitoring/afm-monitoring-public-apis)

- [Manage Permissions](https://docs.mulesoft.com/access-management/managing-permissions)