Cron jobs
Background jobs, scheduled tasks, and long-running work. Built into the codebase with Inngest.
No third-party cron service
Most boilerplates tell you to sign up for some external cron scheduler, paste a URL, set basic auth credentials, and pray it runs on time. That is an extra moving part you do not need.
Background work here runs through Inngest, which is built into the codebase. Scheduled tasks, queues, retries, long-running jobs. It all lives alongside your application code, version-controlled, type-safe, and testable.
What this looks like in practice
A cron job is just a function with a schedule. It runs inside your application, connects to the database directly with a service role client, and handles its own retries if something fails. No webhooks to configure. No passwords to manage. No third-party dashboard to check.
The agents know how to create these. When a build step calls for something like "distribute credits daily" or "send reminder emails every morning," the backend agent writes an Inngest function with the right schedule, retry logic, and error handling.
How to add a scheduled job
Tell the orchestrator what you need. Be specific about timing and what the job should do.
I need a daily cron job that runs at midnight UTC. It should check all users
with expiring trial accounts (trials ending in the next 24 hours) and send
each one a reminder email. If the email fails to send, retry up to 3 times
with exponential backoff. Log each notification to a trial_reminders table
so we do not send duplicates.The system will create the Inngest function, the database table if needed, the email template, and wire everything together. You review, merge, and it runs on schedule.