Skip to content
Aurabase Logo
aurabase

Cron

Schedule the invocation of an Edge Function on a cron expression. Each scheduled run puts a job in the same queue as the asynchronous invocations, consumed by the pool of workers — without retrying in case of failure.

Explanation5 min readLevel intermediateRevised on Aug 15, 2026

One more trigger for your functions#

The aura-functions service can invoke an Edge Function on a schedule, in addition to synchronous HTTP invocations and manually queued asynchronous jobs — see /docs/functions. There is no separate “cron” function: any deployed function can be targeted by a schedule.

Info

Cron schedules Edge Functions (aura-functions), not in-database SQL jobs (pg_cron is not installed in the managed Postgres image). For database maintenance (materialized views, periodic cleanups), schedule an Edge Function that connects to your database via @aurabase/aurabase-js or DATABASE_URL.

Cron enqueues a job, it does not run the function#

A cron run does not launch the function directly: it creates a job in the queue (the same tables and the same worker pool as POST /v1/functions/:projectId/jobs), with a payload frozen at the time of cron creation. The job is then consumed by a worker like any other job.

cycle of a scheduled runtext
TRIGGER   ────▶  the in-process scheduler triggers at the scheduled time
ENQUEUE   ────▶  a job is created (function_name + cron payload)
WORKER    ────▶  the worker pool consumes the job, invokes the function
FAILURE     ────▶  max_attempts=1 → dead (DLQ) immediately, no retry
SUCCESS    ────▶  last_run + next_run updated on cron line
Tip

When the service is restarted, all active crons of all provisioned projects are reloaded from the database and rescheduled — the task list is not persisted in memory alone.

What the scheduler provides#

  • In-process scheduler. tokio-cron-scheduler + the cron crate in aura-functions: no external service, in-memory scheduling rescheduled on startup.
  • Each run is a job. The cron does not execute anything itself: it enqueues a job (like functions.invoke in asynchronous mode), consumed by the same pool of workers.
  • Without retry. A job created by the cron has max_attempts=1: a failure switches it directly to DLQ (dead), unlike classic asynchronous jobs (3 attempts by default).
  • Last_run/next_run tracking. Each trigger timestamps last_run and pre-calculates next_run from the stored expression — visible via listCronJobs().

Create, list, delete#

app/cron.tstypescript
import { createClient } from '@aurabase/aurabase-js'

const aura = createClient(url, serviceRoleKey)

// 5-field expression (min hour day month dsem) — seconds are
// implicitly 0. A 6-field expression (with seconds) is also accepted.
await aura.functions.createCronJob(
  'rollup-15min',      // name, unique per project
  '*/15 * * * *',      // planning
  'rollup',             // function invoked at each run
  { payload: { minutes: 15 } },
)

const { data: crons } = await aura.functions.listCronJobs()
await aura.functions.deleteCronJob('rollup-15min')
Tip

The name of a cron is unique per project and serves as an identifier for deletion (DELETE /v1/functions/:projectId/cron/:nom) — there is no UUID to remember on the client side.

What cron doesn't do (yet)#

No dedicated CLI command

Unlike function secrets (aura secrets), there is no aura functions cron command today: management of scheduled tasks goes through the SDK or the REST API, not through the CLI.

No automatic retry

A job from the cron fails directly in dead (DLQ) on the first attempt — max_attempts is worth 1, compared to 3 by default for a classic asynchronous job. A cron-invoked function must therefore handle its own replays if the underlying operation is to be guaranteed, or you must monitor the DLQ (GET /v1/functions/:projectId/jobs/dlq) and replay manually.

To go further#