Cron Jobs
Cron Jobs are scheduled HTTP tasks that Dashboard.PT calls for you on a schedule. Instead of running a cron daemon on your own server, you register a URL and an interval, and Dashboard.PT triggers it reliably, retries on failure, keeps a full history and tells you if something breaks.
Overview
A cronjob is a URL that Dashboard.PT requests at times you define. It is ideal for triggering recurring work such as cache warmers, report generators, cleanup scripts, data syncs or any endpoint that needs to run on a schedule. Because the scheduling lives in Dashboard.PT, it keeps running even if your own machine is offline.
Key features
- Schedule any HTTP endpoint without maintaining a cron daemon
- HEAD, GET or POST requests with an expected status code
- Automatic retries to ride out transient failures
- Reusable cron templates for common configurations
- Full execution history with status, duration and response
- Failure alerts by email, SMS and/or webhook, plus the notification centre
- Enable or disable a cronjob at any time
Creating a cronjob
Open the Cron Jobs section and select New cronjob. Configure the following fields and save:
- URL: the endpoint to call, including
https://orhttp://. - Schedule / interval: how often the job runs — a simple interval (for example every 15 minutes or once a day) or a specific time.
- HTTP method: HEAD, GET or POST, depending on what your endpoint expects.
- Expected status code: the HTTP code that means the run succeeded, usually
200. Anything else counts as a failure. - Retries: how many extra attempts to make if the first request fails, before the run is declared failed.
- Timeout: how many seconds to wait for a response before the attempt is treated as failed.
- Notifications: choose email, SMS and/or webhook so you are told when a job fails after its retries.
Note: keep each triggered task quick and idempotent. If a task can be safely run more than once, retries never cause side effects.
Cron templates
If you create many similar jobs, cron templates let you reuse a common configuration instead of filling in every field by hand. Save a set of options — method, expected status, retries, timeout and schedule — as a template, then apply it when creating new cronjobs.
- Standardise settings across a group of related jobs.
- Create new jobs in seconds by starting from a template.
- Reduce mistakes by reusing configurations you have already tested.
Execution history and logs
Every time a cronjob runs, Dashboard.PT records the result so you can see exactly what happened. Open a cronjob to review its execution history, where each run shows:
- Status: whether the run succeeded or failed.
- Duration: how long the request took to complete.
- Response: the returned status code and response details.
The history makes it easy to spot patterns — a job that is slowing down, an endpoint that fails at a particular time of day, or a run that returned an unexpected code.
Failure notifications
When a cronjob fails after exhausting its configured retries, Dashboard.PT notifies you so a broken job never passes unnoticed. You can be alerted by:
- Email — a message with the details of the failed run.
- SMS — a short text for jobs you consider critical (subject to plan and SMS credit).
- Webhook — a POST to your own systems or a service such as Slack or Teams.
Every failure also appears in the in-app notification centre (the bell icon in the header). In that notification, the Resource shows the cronjob name, so you can tell at a glance which job failed.
Note: a notification is only sent once all retries have been used up, so a single flaky attempt that later succeeds will not alert you.
Enabling and disabling a cronjob
You can enable or disable any cronjob at any time. A disabled job stays fully configured but is not triggered and raises no notifications — useful during maintenance windows, while an endpoint is being rebuilt, or to pause a job without deleting it. Re-enable it whenever you are ready and scheduling resumes.
Cronjob fields reference
The table below summarises every field you can configure on a cronjob.
| Field | Description |
|---|---|
| URL | The endpoint Dashboard.PT calls, including the protocol. |
| Schedule / interval | How often the job runs, or the time it runs at. |
| HTTP method | HEAD, GET or POST. |
| Expected status code | The HTTP code that counts as a successful run (for example 200). |
| Retries | Extra attempts made before a run is declared failed. |
| Timeout | Seconds to wait for a response before the attempt fails. |
| Notifications | Email, SMS and/or webhook alerts when the job fails after retries. |
| Enabled | Whether the job is currently scheduled or paused. |
Tip: set a couple of retries to avoid alerts on transient blips. A brief network hiccup or a momentary 5xx often clears on the next attempt, so a small retry count keeps your inbox free of noise while still catching real, sustained failures.
Want to try it? The free plan has no time limit.
Create a free account