Scheduled Jobs
A scheduled job is a script that runs on its own, on a schedule you set with a cron expression. Use it for recurring work: a nightly report, a weekly clean-up, or syncing data with another system.
Applies to: Script Master for Jira and Script Master for Confluence Β· Cloud

How it worksβ
Every hour, Script Master checks which jobs are switched on and due. It runs each due job on the Forge back end, through your Companion App, and keeps a record of the run in the job's History.
The script runs as the app, not as a user. It calls Jira or Confluence with api.asApp() and other systems with fetch. These names are ready to use, with no import: api, route, fetch, authorize and console. Script Master keeps the value the script returns with the run, as a return: line in its output.
You can also start a job at once with Run, or try the code in the editor with Test. See Test or run a job now.
Timingβ
- Schedules are in UTC.
- A job runs at most once per hourly check. A schedule such as every 15 minutes still runs about once an hour.
- Forge can start a run up to an hour after its scheduled time.
- A job you create, turn on, or give a new schedule first runs at its next scheduled time. It doesn't catch up on times that passed before.
Schedule a job with cron has the format and examples.
What the list showsβ
| Column | What it shows |
|---|---|
| Scheduled job | The title and description. Select it to open the editor. |
| Status | Whether the job runs on its schedule. |
| Schedule | The schedule in words, and when the job runs next. A job that is off shows Off, so it doesn't run. |
| History | The last runs, oldest on the left. Select one for its details. |
| Last 7 days | Runs per day, failed runs in red, including runs started with Run. |
| Actions | Edit, Version historyβ¦, Run, Turn on or Turn off, Duplicate, Export and Deleteβ¦ |
Limitationsβ
| Limit | Value | What to do |
|---|---|---|
| Scheduled jobs per site | 5 | Let one job do several tasks, one after the other. |
| How often a job runs | At most once an hour | Use a web trigger called by another system for more frequent work. |
| Start time | Up to an hour after the scheduled time | Don't rely on an exact minute. |
| Title | 128 characters | Not applicable |
| Description | 256 characters | Longer text is cut without a warning. |
| Script size | 230 KiB | Move large data out of the script. |
| Kept runs per job | The last 10 | Copy a run's details with Copy as JSON to keep them. |
| Output lines per run | 100 lines of up to 2,048 characters each | Log less, or return a summary. |
| A test run | 24 seconds | A scheduled run may take longer. Keep long work in small steps. |
Scheduled jobs need a configured Companion App. Without one, the tab shows Action Required: This feature cannot function without companion app, and every run fails.
Tasksβ
- Create a scheduled job: write the script, set the schedule and turn it on.
- Schedule a job with cron: the cron format, examples and time zone.
- Test or run a job now: try the code before saving, or start a saved job at once.
- Check a job's runs and failures: what each run records, failed runs included.
Relatedβ
- Set up the Companion App: deploy and connect the app that runs back-end scripts.
- Forge API for server-side scripts:
api,routeand the other globals. - Scheduled Jobs AI prompt: the API reference to give an AI assistant.
- Version history: compare and restore earlier versions of a job.