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. Ask RShift Sites to set one up. For example:
Schedule a daily job at 7 AM that emails me a summary of today's follow-ups.To review your project’s jobs, go to More → Cloud → 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 RShift Sites in the project chat or through SQL, not from the Jobs view.
Project monitoring can alert you when scheduled jobs fail, so you don’t have to check the run history manually.
FAQ
How do I create or delete a job?
Ask RShift Sites 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.
Why didn’t my project pause automatically?
RShift Sites auto-pauses projects on the built-in backend (Cloud) 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 project manually.
Do jobs use credits?
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.