HowlOps
FeaturesHow it worksPricingIntegrationsDocsChangelogContact
Log inStart free
DOCS

FAQ — common errors

Answers to the most frequently asked questions about errors in HOWLOPS.

"Monitor limit exceeded" when creating a monitor

Your workspace has reached the monitor limit for the current tier. Options:

  • Delete unused monitors under Monitors > select monitor > Delete.
  • Upgrade your tier: Settings > Billing > Change plan.

See Tier limits reference for the exact limits per tier.

"Feature not available on your tier"

The feature you tried to use requires a higher tier. The error response includes a required_tier field. See Tier limits reference for a feature-by-tier breakdown.

Monitor is "up" but my site is actually down

Possible causes:

  • Monitor URL is wrong. Verify the URL, including https:// prefix and any path.
  • The monitor is checking a different endpoint. The health endpoint you are checking may return 200 even when the application is broken. Consider adding a content check (keyword match) in the monitor settings.
  • False positive (not yet confirmed). By default, HOWLOPS requires 2 consecutive failures before opening an incident to reduce false positives. The monitor status may show "up" until the confirmation threshold is met.
  • Geographic routing. The prober is connecting from a specific region. If your DNS or CDN routes that region to a different server, you may see a different result than a local curl.

Monitor is "down" but my site is fine

This is a false positive. Common causes:

  • Temporary network issue in the prober region. Single-region probers can experience brief connectivity blips. Enabling multi-region monitoring (Premium+) cross-validates across regions.
  • Timeout too short. If your endpoint occasionally takes more than the configured timeout, it registers as a failure. Increase the timeout under monitor settings.
  • IP blocking. Your server or CDN may be blocking the prober's IP range. Contact support for the prober IP list to add to your allowlist.
  • TLS certificate issue. If the certificate is invalid, expired, or uses an unsupported cipher, the prober treats it as a failure. Check Monitor > SSL tab for certificate details.

"Rate limited" error (429)

You have exceeded the API rate limit. See API error codes reference for limits per endpoint group. Wait for the X-RateLimit-Reset timestamp before retrying.

Heartbeat not resetting after a ping

Possible causes:

  • Wrong slug. Verify the URL you are pinging matches exactly: POST /api/v1/hb/<slug>. The slug is case-sensitive.
  • Authentication. Heartbeat pings do not require authentication by default, but if your workspace requires it, include the Authorization header.
  • Rate limit. Heartbeat pings have a configurable per-tenant rate limit.
  • Invitation links expire after 48 hours. Ask the inviter to resend.
  • If you followed the link but the workspace still does not appear, you may have accepted it into a different account. Try signing out and signing back in with the email address the invitation was sent to.

Export download links expire after 48 hours. Request a new export from Settings > Account > Data export > Request export.

Status page custom domain shows a certificate error

Certificate provisioning can take a few minutes after the CNAME record is verified. Wait 5–10 minutes and reload. If the error persists after 30 minutes, the CNAME may not be resolving correctly. Verify with:

dig status.example.com CNAME

See Set a custom domain for the full setup guide.

API returns 404 for a resource I know exists

HOWLOPS returns 404 for unauthorized access to prevent tenant data leakage (IDOR protection). Verify:

  • You are authenticated as the correct user and workspace.
  • The resource belongs to the workspace your token is scoped to.
  • The resource ID is correct (UUIDs are case-sensitive).

See also

Was this page helpful?