Skip to main content
Jobs are scheduled background tasks, used when your app needs to perform recurring work such as checking for new information, posting updates, or syncing data.
This page is about jobs, the scheduled background work that runs inside the app you built. Looking for a task Lovable repeats on a schedule, such as a weekly summary in a chat? See Automations. The two are different features.
Ask Lovable to set up a job. For example:
To review your project’s jobs, go to More → Database → Manage → Jobs.

Review and control jobs

The Jobs view lists every scheduled job. Click a job to see:
  • Scheduled: the job’s schedule in plain language, for example “Every day at 08:00 AM” or “Every 15 minutes”. Times are shown in your timezone, like the run history. A schedule that can’t be converted keeps its original time and is marked (UTC).
  • Last run: when the job last executed.
  • A run history table showing each execution’s start time, end time, and status (Succeeded, Failed, or Running).
Use Enable or Disable to control a job. A disabled job does not run again until you enable it. The view does not update live. Use Refresh to reload the job list, or the run history’s own Refresh to load new executions. Creating a job, changing its schedule, or deleting one happens by asking Lovable in the project chat or through SQL, not from the Jobs view.
Jobs that run often or take longer to complete can increase credit usage. See Project usage to review what your project’s jobs consume.
Project monitoring can alert you when scheduled jobs fail, so you don’t have to check the run history manually.

How a scheduled job calls your app

A job that triggers work in your app sends it an HTTP request, the same kind of request a visitor’s browser makes. The address the job calls is public. Without a check, anyone who finds it could send the same request and start the work, such as sending your daily summary email. In new Lovable apps created from May 13, 2026, which use TanStack Start, the job calls an API route in your app. In older React + Vite apps, the job calls an edge function. When you ask Lovable in the project chat to set up the job, Lovable makes sure your app starts the work only when a request comes from the job:
  • The job sends a credential with every request, a secret value that works like a password. Lovable stores the credential as a project secret named LOVABLE_CRON_SECRET, so you do not enter the value or need to see it.
  • Lovable adds a check named authenticateCronRequest to the code that receives the job’s request. The check rejects any request without the right credential before the receiving code does any work.
To check a job you set up earlier, ask Lovable in the project chat, for example:
Lovable adds the scheduled-job credential and the authenticateCronRequest check only for projects on the built-in backend. On a project connected to your own Supabase project, you set up scheduled work in Supabase.

FAQ

Ask Lovable in the project chat, for example “Schedule a job that cleans up expired sessions every night at midnight” or “Delete the daily summary job”. The Jobs view is for reviewing, enabling, and disabling jobs, not creating them.
Lovable auto-pauses projects on the built-in backend after a period of inactivity, but scheduled jobs and other background activity keep a project active. If a project only exists to run jobs you no longer need, disable the jobs or pause the database yourself.
Yes. Each run consumes Cloud usage like any other backend work, so frequent or long-running jobs increase the project’s run credit usage. Review the impact in Project usage. You can also ask Lovable in the project chat How do my scheduled jobs affect my Cloud usage? See Ask Lovable what drives your run credit usage.
Once per minute for a job Lovable sets up. Lovable writes the schedule as a five-field cron expression: minute, hour, day of month, month, day of week.A job that runs at most twice an hour starts a few seconds after its scheduled minute, up to 29, which spreads load across projects. The offset is the same every time for that job. The offset applies to jobs that call an API route in your app, not to jobs that call an edge function.A database-only job you write in SQL yourself can run more often than once a minute, with an interval schedule such as 30 seconds.
The call the job makes times out after a few seconds, and your app’s handler is cancelled with it.A job that takes longer has to start the work, answer the call, and finish the work outside that request. Ask Lovable in the project chat to build it that way.
Not on its own. Ask Lovable in the project chat to delete completed run history, and each request removes up to 10,000 finished runs from before a date you choose. Lovable asks you to approve it, and runs that are still going are left alone.It does not clear the history of HTTP responses, and it does not shrink the disk your database has already been given. Lovable does not recommend a standard retention period, so pick one that meets your support and audit needs.
Your project’s job definitions contain the credential, so treat the ability to read them as access to it. Do not put a credential in a migration file or in the project chat. See How a scheduled job calls your app.