Recurring jobs on CloudBolt Documentation

Manage recurring jobs

Mon, 01 Jan 0001 00:00:00 +0000

Cloud Management Platform (CMP) ships with a set of built-in recurring jobs. Any that you or another administrator create appear alongside them.

View recurring jobs

Go to Admin > Recurring Jobs.

(opens full-size image in a new tab)

The Next Run column shows when each job runs next, or Disabled if the job is switched off. The toggle in the Actions column enables or disables a job.
Select a job name to open its details, including its execution history.

(opens full-size image in a new tab)

Create recurring jobs

Mon, 01 Jan 0001 00:00:00 +0000

Every route starts in the same place: Cloud Management Platform (CMP), at Admin > Recurring Jobs.

Ways to add a recurring job

Add from Job. Turn a job type that CMP already runs, such as a resource handler sync, into a scheduled job.
Add from Action. Schedule an action, either one that already exists on your instance or a new one you define as you go.
Add from Action in Repository. Create the job from an action held in a connected source code repository. CMP opens the new recurring job when it finishes.
Upload Recurring Job. Import a recurring job from a Zip file. Selecting replace existing overwrites any matching action already on the instance.

(opens full-size image in a new tab)

Built-in recurring jobs

Mon, 01 Jan 0001 00:00:00 +0000

CMP ships with a set of recurring jobs you can use as-is, customize, or disable. Several support core functionality, such as resource handler synchronization. Each job is listed below, and the ones you are most likely to configure are described in full further down the page.

The default settings below are for a newly installed instance. Check Admin > Recurring Jobs for the current state of your recurring jobs.

Recurring jobs with secrets

Mon, 01 Jan 0001 00:00:00 +0000

A recurring job created from an action can hold secrets: values of action inputs whose type is password or encrypted text. When you export that job from Cloud Management Platform (CMP), you can encrypt those values with a password you choose. Importing the job prompts for the same password, which decrypts the secrets.

Why use a password

Setting your own password lets you move an exported job between CMP instances without exposing its secrets.