Understanding Scheduled Jobs
- 22 Feb 2023
- 6 Minutes to read
- Print
- DarkLight
Understanding Scheduled Jobs
- Updated on 22 Feb 2023
- 6 Minutes to read
- Print
- DarkLight
Article Summary
Share feedback
Thanks for sharing your feedback!
Overview
Scheduled Jobs is a feature where users can run a Flow, run a Report, send emails, synchronize Active Directory, or perform other tasks on the scheduled date and time. By using advanced scheduling options, a job may be scheduled for almost any frequency.
Users can Enable or Disable Schedule Jobs on a Server. To do so, navigate to System (gear icon) > Administration > Servers. This will show all the servers. Right-click on the Server Name > Edit Server > Under Server Info > Enable or Disable 'Can be Job Server'.
Accessing Scheduled Jobs
In the Designer Studio, navigate to the System > Jobs And Events > Scheduled Jobs. On the Scheduled Jobs Page, any options listed on the Global Action Bar can be used to create the specific Scheduled Job type. Each Scheduled Job has unique settings that help determine what the job does.
Types of Scheduled Jobs
- Scheduled Flows
- AD Sync Jobs
- Interval Jobs
- Startup Jobs
- Thread Jobs
- Email Response Scheduled Jobs
Scheduled Flows
The New Schedule Flow option will allow users to run a Flow per the required date, time, and span. It has the option to pick an already created Flow or to create a new Flow.
Configurations for Scheduling a Flow
| Configuration | Description |
|---|---|
| Scheduled Job Name | This will set the Name of the Scheduled Job |
| Pick or Create Scheduled Flow | This will allow the user to pick an existing Flow or create a new Flow |
| Calendar | This option allows users to configure the calendar type and its calendar information for precise job scheduling. |
| Daily Schedule | Allows to run the job daily.
|
| First Day of Month | Allows to run the job on the first or last day of the month, respectively.
|
| Monthly Schedule | Allows the job to run once every Month
|
Specified Job Schedule | Allows running the job at a specific time.
|
Time Span Schedule | Allows running the job at a fixed interval of time span
|
Weekly Schedule | Allows the job to run once every Week.
|
Yearly Schedule | Allows the job to run once every Year.
|
| Requeue if Job Fails | If the Job fails, this action will restart the job after completing all the jobs from the same job queue. Job Queue: A Job Queue will contain a set of jobs running one after the other. Consider this as a single basket of Jobs. If a Job gets held up, all scheduled jobs in the same queue will be put on hold until the initial job finishes. |
| Create Task if Job Fails | This action will allow notifying, creating, and assigning a task for a user if the job fails. |
| Run Job on Startup | This will start the job whenever the Decisions Server is restarted.
|
| Start Date | This will set the date and time to start the job |
| Specify Expiration | This will expand and allow setting the date and time to expire the job. |
| Override Job Queue Name | This will allow setting a new Queue Name. Queue Name: If the Queue name is the same for multiple jobs, it will be considered a single Job Queue. So to run the Jobs in parallel, users need to give a new Queue Name to create a new Job Queue. |
| Notify on Job Delay | When this option is enabled, users can set up notifications for delays in their job by configuring the relevant details. |
| Delay Greater than (in seconds) | This is a buffer period before notifications are sent to users regarding job delays. |
| Add to Logs | This feature allows for adding logs to the log folder and setting the level of logs included in the logs. |
| Emails | This will trigger an email notification to the configured email addresses, informing them that the job has been delayed. |
| Create Assignments | This will create user and group assignments regarding the delayed job. |
Refer to the following article to learn about Running a Flow as a Scheduled Job.
AD Sync Jobs
To learn all about the Active Directory (AD) and Active Directory (AD) sync Jobs, refer to the following Documentation:
Interval Jobs
The Add Interval Job option allows users to run a Flow, usually at specified intervals.
Configurations for Interval Job
| Configuration | Description |
|---|---|
| Job Name | This allows setting the Name of the Job |
| Enabled | When selected, this will ensure that the Interval Job is active and running. |
| Pick Flow | This will allow the user to pick an existing Flow |
| Only Run on Job Server | When Enabled, this will run the Job only on one server from the clustered environment. |
| Count | Number of times the job will run at once |
| Interval | Adjust the Sliders to set the interval time |
| Notify on Job Delay | When this option is enabled, users can set up notifications for delays in their job by configuring the relevant details. |
Delay Greater than (in seconds) | This is a buffer period before notifications are sent to users regarding the job delay. |
| Add to Logs | This feature allows for adding logs to the log folder and setting the level of logs included in the logs. |
| Emails | This will trigger an email notification to the configured email addresses, informing them that the job has been delayed. |
| Create Assignments | This will create the assignments to the users and groups regarding the delayed job. |
Once all the settings are configured, the Interval Job will start instantly. To learn more about Interval Jobs, refer to Interval Jobs.
Startup Jobs
The Add Startup Job option allows users to run a Flow when the Decisions Server is restarted.
- Self-Hosted: Restarting the Decisions Server from Windows Services
- IIS Hosted: Restarting the Decisions Server by entering 'iisreset' from the Command Prompt/PowerShell
Thread Jobs
Thread Jobs shows all the Decisions internal Job Processes.
Was this article helpful?
