5.17 Schedules

Once you have configured a module you must configure a job. A job is made up of a Schedule, Worker and Profile.

Schedules define when to perform the data collection as defined in a job. a job defines what schedule, profile and worker to use.

  • You can create as many schedules as you need.

  • Schedules have no functionality until they are associated with one or more jobs.

  • They can be shared across multiple jobs.

  • You cannot delete a schedule that is currently associated with a job.

  • Schedules can be recurring or one-time.

Single schedules are configured with one start time, and one date.

To keep jobs from queuing up to the worker, enable (check) "If time assigned for job start has elapsed, don't resend job". Otherwise, a job will queue up on the worker if a previous job has not yet completed, causing the new job to start as soon as the current job is complete or terminated.

Recurring schedules are configured using a start and interrupt time, and which days to start on.

Choose when on which days you want this schedule to trigger a job.

You may specify maximum job duration. If the job runs longer than the time limit you set, it will be interrupted. For cases where you do not want the job to be interrupted. In an example with a job you know will last longer than 22 hours, you may prevent the schedule from interrupting the job.

Don’t forget to “Save Changes”.

In the user’s archive the folder will be called: In-network SMS. And will contain SMS and MMS messages from the carrier.