Table of contents

How we run checks

Checkly runs your API & browser checks every x minutes, based on an interval you select. We have different minimum intervals for each check type:

• API checks can be scheduled to run every 10 seconds.
• Browser checks can be scheduled to run every 1 minute.

You can select one or more data center locations to run your checks from. We advise to always select at least 2 locations. There are two reasons for this:

1. Redundancy: we might have an issue in one location, but not the other.
2. Retrying: if your check fails, we will execute its retry strategy where you have the option check from a different location. This location is picked from your configured locations.

You can choose to run your check in parallel or round-robin. Read more about scheduling strategies here.

A picture is a thousand words:

1. A cron process picks up a check based on its schedule, say every 5 minutes. It validates that the check is not in progress at the moment to avoid race conditions. The check is put into a queue to be run from the next configured data center location.
2. If the check is an API check and has a setup script, the setup script is executed.
3. The check is executed.
4. If the check is an API check and has a teardown script, the teardown script is executed. Teardown scripts are run before any assertions are validated.
5. The result is stored in our central database.
6. If the check fails, its retry strategy is executed. Based on the retry strategy, a check is retried one or multiple times. Any setup & teardown scripts are run again as part of the process.
7. Alerts are sent out in requested channels when the sequence is complete. It’s considered complete when the check run was successful or the final attempt was executed. We will send alerts only if the final attempt has failed (no alerts sent for the initial attempts)

Last updated on April 25, 2024. You can contribute to this documentation by editing this page on Github