← all problem types

monitor_run_refused

409 Conflict   The monitor cannot be run right now.

When you get it

The monitor cannot be run right now. It is always answered with HTTP 409 - one code means one status, so a client may key its handling on either.

Fields it carries

Inside each errors[] entry, beside pointer:

reason

The machine-readable sub-case, when one code covers several. Branch on it.

retryAfter

How long to wait before retrying, in seconds. Mirrors the Retry-After header.

nextAllowedAt

When the next manual run of this monitor will be accepted.

A field is omitted when the server genuinely does not know it - an absent member is never the same as an empty one.

How to fix it

The request conflicts with the resource's current state. Re-read the resource and decide, rather than retrying blindly.

Shape

{
  "type":   "https://api2.host-tracker.com/problems/monitor-run-refused",
  "title":  "The monitor cannot be run right now.",
  "status": 409,
  "code":   "monitor_run_refused",
  "errors": [
    { "reason": …, "retryAfter": …, "nextAllowedAt": … }
  ]
}