Benefits

• Automate the submission of jobs
  Using Cron, you can automate job submission to the Job Pool. No matter how versatile your requirement, you can configure your cron either through code using Catalyst SDKs (Java, Node.js, and Python) or using the UI Builder in the console and the job will be created automatically as per your configurations. Since the cron daemon is constantly running in the background, Catalyst will ensure that the job is created promptly and submitted to the Job Pool without any delay.

• Configure cron during runtime
  Using Dynamic Crons you can configure and schedule both one-time and recurring crons dynamically during application runtime. Dynamic crons can be created through code. Catalyst also offers you the required SDK support in Java, Node.js, and Python runtime. Catalyst also offers you REST APIs to perform cron operations. Since these crons are generated dynamically during runtime, your crons will be active only when they are required. This further optimizes your application.

• Cron Expressions allow for more flexibility
  Using Cron Expressions allows you schedule crons with greater precision and flexibility. For example, you can configure a cron that will submit jobs to the Job Pool on every third day of the calendar month of a calendar year. You can further drill down and schedule the cron to submit a job every minute of a particular hour of any day of the calendar month in a calendar year. Achieving this level of versatility is quite simple using Cron Expressions.

• Cron Expressions allow hassle-free migration of crons from other services to Catalyst
  Cron expressions are regex-like standard expressions. Migration of your codebase from one service to another is a cumbersome experience. But when it comes to migration of your cron jobs from other services to Catalyst, you can easily reconfigure them in your codebase itself using Cron expressions. Catalyst also offers you SDKs in Java, Node.js, and Python with the necessary code snippets and functions to configure cron using Cron Expressions.

• Execution History
  Catalyst logs every cron that is executed and makes them immediately available in the Execution History section. These logs enable you to assess the performance of your crons, debug errors and perform quick fixes, and make informed decisions based on analytics and reports. The execution history is available for 15 days in the Development environment and 30 days in the Production environment.

• Adept at failure handling
  Sometimes, due to external factors, failures in cron execution can occur. However, with Job Scheduling’s Cron, you always have the option to configure a maximum of 10 retry attempts. You can configure these retries with a minimum interval of 1 minute to a maximum of 24 hours. If your cron execution has been canceled due to a loss of network or other such external factors, a retry attempt can solve the issue automatically. Furthermore, if the execution failed even after multiple retries, each of the executions is logged in the Execution History, allowing an easier and more informative debugging process.