Frequencies & Scheduling

Every monitor has a frequency that determines how often the hub schedules it for execution.

Setting a frequency

Frequency is a required field in both builders:

import { Frequency } from "@griffin-app/griffin";

createMonitorBuilder({
  name: "health-check",
  frequency: Frequency.every(5).minutes(),
})

Available intervals

Frequency.every(1).minute()    // Every minute
Frequency.every(5).minutes()   // Every 5 minutes
Frequency.every(15).minutes()  // Every 15 minutes

Frequency.every(1).hour()      // Every hour
Frequency.every(6).hours()     // Every 6 hours

Frequency.every(1).day()       // Every day
Frequency.every(7).days()      // Every 7 days

Both singular and plural forms work: .minute() and .minutes() are equivalent.

How scheduling works

The hub’s scheduler runs on a tick interval (default: 30 seconds). On each tick, it checks which monitors are due based on their frequency and last execution time, then enqueues jobs for execution.

A monitor with Frequency.every(1).minute() will be scheduled approximately every 60 seconds
The scheduler ensures no duplicate jobs are created for the same monitor within its frequency window
If an executor is unavailable, jobs queue up and execute when an executor becomes available

Choosing a frequency

Frequency	Good for
Every 1 minute	Critical health checks, payment APIs, auth endpoints
Every 5 minutes	Important API endpoints, core business flows, browser page checks
Every 15 minutes	Standard monitoring, CRUD operations
Every 30 minutes	Browser login flows, multi-step UI tests
Every 1 hour	Low-priority checks, third-party API status
Every 1 day	Periodic validation, data integrity checks

Higher frequencies mean more executions, which affects resource usage on self-hosted deployments and costs on Griffin Cloud.

Browser monitor frequency

Browser monitors require a minimum frequency of 1 minute. API-only monitors have no minimum. This constraint is enforced at build time — calling .build() will throw an error if a browser monitor’s frequency is less than 1 minute.

// ✅ Valid — browser monitor at 5 minutes
createMonitorBuilder({
  name: "page-check",
  frequency: Frequency.every(5).minutes(),
})
  .browser("check", BrowserAction({ ... }))
  .build();

// ❌ Throws at build time — less than 1 minute
createMonitorBuilder({
  name: "too-fast",
  frequency: Frequency.every(30).seconds(),
})
  .browser("check", BrowserAction({ ... }))
  .build();

Browser monitors are more resource-intensive than API monitors because they launch a real browser. Choose a frequency that balances monitoring coverage with execution cost.

Locations

Optionally specify where your monitor should execute. In distributed mode, jobs are routed to executors running in the specified locations:

createMonitorBuilder({
  name: "global-check",
  frequency: Frequency.every(5).minutes(),
  locations: ["us-east-1", "eu-west-1"],
})

When locations are specified, the scheduler creates separate jobs for each location on each run. If no locations are specified, the monitor runs on any available executor.

Getting Started

Concepts

Writing Monitors

Platform

Griffin Hub

Griffin Cloud

Command Line

Frequencies & Scheduling

Setting a frequency

Available intervals

How scheduling works

Choosing a frequency

Browser monitor frequency

Locations

​Setting a frequency

​Available intervals

​How scheduling works

​Choosing a frequency

​Browser monitor frequency

​Locations

Setting a frequency

Available intervals

How scheduling works

Choosing a frequency

Browser monitor frequency

Locations