● Alwaysbeat

Help

FAQ & troubleshooting

Answers to common questions and the usual reasons a check misbehaves.

My job runs but the check never went "up"

I get "down" alerts even though the job ran

Does the ping have to be a GET? Do I need a body?

No. Any method works (GET, POST, HEAD) and no body or headers are required. A bare GET is the normal case.

Is the ping URL a secret?

Yes — anyone who knows a check's ping URL can ping it. Keep it out of public repos and logs. For public README badges, use the badge URL, which uses an opaque token instead of the real check ID.

How do I stop alerts during maintenance?

Pause the check. Paused checks are never marked down. Resume when you're done.

Should a failed ping break my job?

No. Treat the ping as telemetry, not a dependency. Don't let a non-2xx ping response abort the real work — log it and move on. A short timeout plus a couple of retries is the right balance.

How long is history kept?

Recent events (pings and transitions) are visible on each check's page and via the events endpoint. Older event-log rows are pruned over time; the check's current status and schedule are always retained.

Can I get alerts in Slack?

Yes — add a slack: channel with a Slack Incoming Webhook URL and Alwaysbeat posts formatted alerts to that channel. See Notifications → Slack for the setup steps.

How do I delete my account?

In the dashboard, go to Settings and use the Danger zone at the bottom of the page. Deleting your account permanently removes all your checks, their history, and your API keys.