Scheduled jobs

Some work should happen on a timer, not a click. Scheduled jobs run a backend function on a recurring schedule.

You'll find them under Settings → Cloud → Jobs.

Set a schedule

Describe the cadence in plain English and Vorx configures the trigger:

Every Monday at 9am, email each manager a summary of their team's open tasks.

Say the timezone if it matters to you — "9am UK time" — otherwise a schedule may not fire when you picture it firing.

Common uses

• Digests — daily or weekly summary emails.
• Cleanups — archive stale records.
• Syncs — pull from or push to another system on a cadence.
• Reminders — nudge users about due dates.

Be careful with cleanups

A job that deletes is the one to think hardest about, because it runs unattended and repeatedly. Prefer archiving or marking inactive over deleting, scope the job as narrowly as you can, and check the first few runs in the logs before you leave it alone.

Reliability

Each run is independent and recorded, so a single failure doesn't stop future runs. A job that fails every time will keep failing every time, though — which is why the first check matters.

Watch runs

Every execution shows up in the job's run history — Settings → Cloud → Jobs, then open the job — with its status, so you can confirm the job fired and catch errors early. A job that silently stopped doing anything is much easier to spot here than in your app.

Next steps

• Backend functions — what a job runs
• Logs and monitoring — confirming it fired
• APIs and automations — event-driven work