Skip to content

5.3Grace periods

Jobs are rarely exactly on time. Grace is the extra time a job gets before obsrvly marks it down. The setting depends on the schedule.

SettingScheduleDefaultAllowed values
grace periods (API: gracePeriods)IntervalDashboard: 2
API: 1
Dashboard: 1–100
API: up to 1000
grace seconds (API: graceSeconds)Cron300 (5 minutes)0 to 2,592,000 (30 days)

Grace periods (interval)#

grace periods is the number of intervals that may pass between two pings. With expected every 5 minutes and grace periods 2, each ping must come within 10 minutes of the last one.

With 1, the next ping is due exactly one interval after the last one. A job that runs a few seconds late then goes down. Use 2 or more for most jobs.

Form errors: Required when the field is empty, and 1–100 when the value is out of range. Through the API, 0 or no value means 1. A value above 1000 gets invalid input: grace_periods can be at most 1000.

Grace seconds (cron)#

grace seconds is how late a run may report, counted from each scheduled time. If you leave it empty or enter 0, obsrvly allows 5 minutes. The monitor page shows the grace only when you entered a value.

  • The finish ping is what counts. Set grace seconds longer than the job usually takes. A backup that takes 20 minutes needs more than 5 minutes, for example 1800.
  • Keep grace seconds shorter than the time between runs.
  • Negative values get Cannot be negative. Values above 30 days get invalid input: grace_seconds can be at most 2592000 (30 days).

Last updated