Cron jobs
Run recurring work on a schedule — nightly cleanups, hourly syncs, weekly reports. A cron job either hits an HTTP endpoint or runs a command inside your project's container.
Schedule
Jobs use standard cron expressions with timezone support. The dashboard validates your expression and previews the next runs as you type:
0 9 * * 1 # 09:00 every Monday
*/15 * * * * # every 15 minutes
0 0 1 * * # midnight on the 1st of each monthJob targets
- HTTP — Orizon makes a signed request (GET / POST / PUT / PATCH / DELETE) to a URL you choose, with optional custom headers and a body. Requests carry an HMAC signature so your endpoint can verify they came from Orizon.
- Command— Orizon runs a shell command inside your linked project's container, so the job has your app's code and environment available.
Retries & history
Each job has a configurable timeout and a retry count (with backoff) for transient failures. Every run is recorded — trigger, status, HTTP code or exit code, duration, and response — so you can see exactly what happened. You can also trigger a job manually at any time.
Failure alertsCron failures can notify you over the WhatsApp bot, so you hear about a broken job without watching the dashboard.