Cron Jobs

Through our Customer Center, you can create cron jobs based on HTTP requests or SSH commands. To manage your cron jobs, first log in to the Customer Center at account.creoline.com using your credentials, then navigate to the Tools → Cron Jobs menu item.



Create a Cron Job

To create a new cron job, click the Create Cron Job button.



Our cron jobs support the following types:


Type Description
HTTP Request In this mode, an HTTP request is sent to the specified URL at the defined interval.
SSH Command In this mode, an SSH command is executed on the target server at the specified interval.
Guest Agent Command In this mode, a direct shell command is executed on the target server at the specified interval.


Please ensure that incoming TCP connections to the target server are allowed if you are using the “HTTP Request” or “SSH Command” type. A list of our IP ranges can be found below.




The execution interval can be configured as either relative or absolute. To define more complex time intervals, first save the cron job using one of the predefined intervals, and then select the Change Interval button in the Interval section.



Then adjust the desired interval in Cron style and select the desired time zone. New cron jobs are automatically created in Coordinated Universal Time (UTC).



Edit Cron Job

Select a cron job to open its overview. From this view, you can adjust individual settings of the cron job or schedule it to run immediately.



Action Description
Pause Cron Job Pauses the job until it is manually reactivated
Run Cron Job Immediately Runs the job regardless of the currently defined interval
Edit Master Data Modifies the cron job’s master data, such as name or status
Edit HTTP Request Modifies the target URL, the expected HTTP status code, or timeouts
Edit Interval Modifies the interval
Delete Cron Job Deletes the cron job


If the cron job is deleted, it may take up to five minutes before no further executions are triggered.



Notifications

Using notifications, you can trigger emails, SMS messages, or webhooks depending on whether the cron job ran successfully or failed.

To do this, go to the Notifications tab and click Add Notification.


Supported Channels:

Channel Supported Events
Email Successful, Failed, Timeout, Overlap
Webhook Successful, Failed, Timeout, Overlap
SMS Successful, Failed, Timeout, Overlap


When creating the notification, select the desired channel and enable the events you want to trigger this notification.




IP Address Range for Cron Job Execution

Please ensure that the following IP addresses are allowed by your cloud or software firewall for the execution of the cron job.

  • 5.1.73.54
  • 5.1.73.91
  • 5.1.73.92
  • 5.1.73.93
  • 5.1.73.94
  • 5.1.73.95
  • 5.1.73.96
  • 5.1.73.97
  • 5.1.73.98


For the HTTP call, incoming TCP connections on ports 80 and 443 should be enabled. Cron jobs of the SSH command type, on the other hand, require incoming TCP connections on port 22.

No firewall rules are required for the Guest Agent Command type.


If the target server is a creoline server, instead of manually specifying individual IP addresses, you can use the dynamic firewall ruleCronjob Server.” This dynamic firewall rule automatically allows all cronjob servers.



Frequently Asked Questions


What happens if a job takes longer than the set interval, causing subsequent jobs to overlap?

Our cron job system automatically detects if a job is running longer than the set interval and skips the scheduled execution if the last execution has not yet completed.


What happens if the execution takes longer than the set timeout?

If the cron job cannot be completed within the set timeout, the execution is considered an error and logged with status 124 in the execution log. Increase the timeout value or adjust the cron job so that it finishes sooner. If the cron job continues to return a status code of 124 despite the maximum timeout of 10,800 seconds (3 hours), the cron job should be optimized to ensure that its runtime is less than 3 hours.