Configuring Scheduled Jobs
This page covers the field-by-field reference for creating and editing a Scheduled Job, plus the day-to-day admin actions: cloning, deleting, and running a job manually.
Requirements
- Administrator System Role.
Creating a Scheduled Job
- Go to Setup > Manage > Scheduled Jobs.
- Click New.
- Complete the fields described below.
- Click Save. To create another after saving, click Save & New.
Field Reference
| Field | Required | What It Does |
|---|
| Action | Yes | The URL path the job invokes when it fires. Example: /sys/usergroup/RecalculateMembersForAllGroups. The path is invoked server-side with the current portal's context; anything a controller action can do can be scheduled. |
| Interval | Yes | How often the job runs, expressed in minutes. There is no picklist — enter 60 for hourly, 1440 for daily, 10080 for weekly. Interval = 1 (every minute) is supported but rarely useful. |
| Starts On | Yes | The earliest UTC date/time the job may fire. The job will not run before this timestamp. Convert your local time to UTC before entering. |
| Ends On | No | The UTC date/time after which the job stops firing. Leave blank for a job that runs indefinitely. |
| Auto Adjust Duration | No (default on) | When enabled, the platform can increase frequency during high-volume periods (up to once per minute) and back off to your configured Interval during low-volume periods. Disable for jobs whose cadence must be exact. |
| Enabled | No (default on) | Master on/off switch. When off, the job stays in the list but never fires. |
| Owner | No | Lookup to a User. Defaults to the admin who creates the job. Ownership is administrative — it does not change what runs. Note: this field must be added via Edit Layout to appear on the Cron Job New/Edit/detail form. |
| Description | No | Free-text notes about what the job does and why. Useful when your portal accumulates many jobs. |
| Auto Delete | No (default off) | When checked, the job record is automatically deleted after it completes a successful run — commonly used for one-time jobs (see One-Time Jobs below). Note: this field must be added via Edit Layout to appear on the Cron Job New/Edit form. |
| Job Type | No | Optional label. Set to Report run for scheduled-report jobs, or leave blank / set to Generic for anything else. This is a categorization aid, not a functional switch. Note: this field must be added via Edit Layout to appear on the Cron Job New/Edit form. |
| Is Standard | Host-only | Marks a job as a system-shipped standard job. Only Host users can change this; administrators cannot. Admin-created custom jobs are non-standard by default. Note: this field must be added via Edit Layout — for any user, including Host — before its value can be viewed or changed. |
| Status, Last Fire Time | System-managed | Read-only. Status values, when they update, and what each means are covered in Scheduled Jobs Troubleshooting. Note: the default Cron Job detail layout shows Status and Last Fire Time. Start Fire Time must be added via Edit Layout to become visible. |
Editing an Existing Job
- Go to Setup > Manage > Scheduled Jobs.
- Click the job's Name to open its detail page.
- Click Edit.
- Adjust the fields, then click Save.
Any field except Status, Last Fire Time, and Start Fire Time is editable. Changes apply on the next dispatch cycle.
Cloning a Job
To create a new job with the same Action but a different schedule or a different set of query-string parameters:
- Open the source job's detail page.
- Click More Actions > Clone.
- Adjust any fields you want to change on the clone.
- Click Save.
Deleting a Job
- Open the job's detail page.
- Click Delete. This is a standalone button next to Edit on the detail page.
- Confirm the deletion when prompted.
Deleted jobs go to the Recycle Bin (subject to the standard 30-day retention). Standard jobs shipped with the platform can be deleted by an admin, but cannot be recreated from Setup — contact support to restore one.
Running a Job Manually (Run Now)
You can force a job to execute immediately without waiting for its next scheduled fire:
- Open the job's detail page.
- Click More Actions > Run Now. Run Now is located inside the More Actions menu.
- The job's Status flips to Processing. Wait for it to return to Idle; the Last Fire Time updates to reflect the manual run.
Running Now does not shift the recurring schedule — the job continues to fire at its normal interval afterwards. For actions that fail quickly, Status typically goes straight to Failed, skipping the visible Processing state. If the manual run fails, an entry is written to Setup > Manage > Event Logs with the details.
Time Zones
All timestamps on a Scheduled Job are stored and evaluated in UTC. To schedule a daily job to fire at 06:00 in a specific time zone, convert to UTC and set Starts On accordingly. There is no per-job or per-org time-zone override.
One-Time Jobs
To schedule a one-time job that runs once and then disappears:
- Set Starts On to when you want it to run.
- Set Ends On to a short window after Starts On (for example, one hour later).
- Set Interval to a large number (for example, 1440) so it will not re-run inside its window.
- Check Auto Delete so the row is removed after it completes.
<< Standard Scheduled Jobs | Scheduled Jobs Troubleshooting >>