Running a Manual Check

Running a Manual Check

A manual check triggers an immediate on-demand HTTP request to your monitor's endpoint, outside of the normal scheduled interval. The result appears in your check history just like a scheduled check.

When to Use a Manual Check

  • After making a configuration change — confirm that headers, auth, or body changes are working correctly before the next scheduled check
  • After a deployment — verify the endpoint is healthy right now without waiting for the next interval
  • During troubleshooting — get an immediate data point when investigating a problem
  • After setting up a new monitor — confirm PulseAPI can reach the endpoint

How to Run a Manual Check

  1. In the left sidebar, click Monitors.
  2. Click the monitor you want to check.
  3. On the monitor detail page, click Run Manual Check (or Check Now).

PulseAPI sends the request immediately. The result appears in the Check History section at the bottom of the page within a few seconds.

What the Result Shows

The manual check result is recorded identically to a scheduled check:

  • Status — Up or Down (with specific failure type if down)
  • HTTP status code — the code returned by the endpoint
  • Response time — how long the request took in milliseconds
  • Error message — if the check failed, the reason

A manual check is labeled in the check history so you can distinguish it from scheduled checks.

Does a Manual Check Trigger Alerts?

A manual check follows the same alert rule evaluation logic as a scheduled check. If the manual check fails and matches an active alert rule (and the cooldown has elapsed), an incident will be created and notifications sent.

Related Articles

Still have questions? Contact support.

    • Related Articles

    • Viewing Check History

      The check history is a log of every HTTP request PulseAPI has made to a monitor. It's the primary tool for diagnosing problems, understanding patterns, and reviewing past incidents. How to Access Check History In the left sidebar, click Monitors. ...

    • Check Intervals Explained

      The check interval is how often PulseAPI sends a request to your monitor. This article explains what intervals are available, how your plan affects them, and how to choose the right interval for each monitor. What Is a Check Interval? Every monitor ...

    • Check Interval Limits by Plan

      The fastest check interval available to you depends on your plan. This article explains what each plan supports and how to get faster checks. Minimum Intervals by Plan Plan Minimum Interval Available Options Free 60 seconds 60s only Starter 60 ...

    • Authentication Options for Monitors

      If the endpoint you want to monitor requires authentication, PulseAPI needs to send credentials with each check. This article explains the supported authentication methods and how to configure them. Option 1: Basic Authentication Basic auth sends a ...

    • Searching and Filtering Monitors

      When you have many monitors, the search and filter tools help you find specific ones quickly. Searching by Name or URL On the Monitors list page, a search bar appears at the top. Type any part of a monitor's name or URL. The list filters in real time ...