Got questions?

Jobs fire within seconds of the scheduled time. We use distributed infrastructure with sub-minute precision, not cron-based rounding.

The delivery is retried automatically with exponential backoff. Current plans use the same reliable retry policy: up to 3 retries, with every attempt logged with its HTTP status, latency, error, and response body when available.

You can cancel any pending job via the API or dashboard before it fires. Jobs cannot be modified after creation; cancel and recreate if you need to change the payload or timing.

The job is marked as failed and the full delivery history remains visible in your dashboard: every attempt, status code, latency, error, and response body when available.

Logs include the scheduled job metadata, each delivery attempt, HTTP response codes, latency, errors, and response bodies when available. Plan-specific retention automation is not advertised until it is fully wired to production cleanup jobs.

All plans run on the same production delivery path. A formal SLA is only available through a separate written agreement, so the public plans do not promise an automatic contractual SLA.

One scheduled HTTP request equals one job, regardless of retries. If a job fails and retries several times, it still counts as one job against your monthly limit.

Yes. The Free plan requires no payment method. You get 1,000 jobs/month, API access, delivery logs, and dashboard scheduling, enough to integrate and test end-to-end before upgrading.

Yes. Upgrades take effect immediately and are prorated. Downgrades apply at the start of the next billing cycle. No contracts, cancel anytime.