Job Settings

This topic presents the setting options available for your job.

You can access the job settings from the The "Overview" page icon is a square divided into several other squares. Overview page of the job.

Job settings from the "Overview" page.

It includes the following non-versioned and editable features:

1 – Name

Names are mandatory, with a maximum of 255 characters, and unique within a project.

2 – Alias

The job alias is optional and unique for each job within a project. It allows you to refer to a job within another job, and can be used in pipelines when the settings env vars Variables setting is enabled.

3 – Description

Descriptions are optional and have no restrictions, but it is a good practice to add them and keep them short and informative.

4 – Scheduled run Icon for runtime types is a calendar.

There are two runtime types:

  • The manual run, which requires you to click Run to start the job.

  • The scheduled run, which launches the job according to the schedule you choose.

    Scheduled jobs can also be started manually.

    The Scheduled run type has three schedule modes: Simple, Shortcut, and Expert.

    • In Simple mode, you can easily specify variables through the user interface. There are many possibilities.

      Screenshot of the settings for the scheduled run type in simple mode

    • In Shortcut mode, you can choose the recurrence of your run on an hourly, daily, weekly, monthly, or annual basis. All other settings are automatic.

      Screenshot of the settings for the scheduled run type in shortcut mode

    • In Expert mode, you can specify variables using the Cron format. The Cron time string consists of five values separated by spaces: [minute] [hour] [day of the month] [month] [day of the week]. They are based on the following information:

      Table 1. Cron format
      Descriptor Acceptable values


      0 to 59, or *


      0 to 23, or *

      Day of the month

      1 to 31, or *


      1 to 12, or *

      Day of the week

      0 to 7 (0 and 7 both represent Sunday), or *

      The Cron time string must contain entries for each character attribute. If you want to set a value using only minutes, you must have asterisk characters for the other four attributes that you are not configuring.

      Screenshot of the settings for the scheduled run type in expert mode

      Once you have finished scheduling your run, you will see the summary of your choice written below and the time of the next run.

Regardless of the Scheduled run type that you selected, you can specify the time zone for your jobs or pipelines. When specifying its time and day, you should know that:

  • The default value in the time zone selection is your browser’s time zone.

  • The next schedule preview will be displayed in the time zone of your browser.

  • Daylight Saving Time (DST) is automatically adjusted.

  • Runs scheduled for the 29th, 30th, or 31st day of the month will not run in months with less than 29, 30, or 31 days.

    Example 1. French time settings

    UTC time is two hours behind French time, so if you want your job to run at midnight French time, set it to two hours later, that is, at 2 a.m.

5 – Alerts The "Alerts" icon is a bell.

Alerts are optional and can be set to receive an email when the status of your job changes. They can be sent to multiple email addresses to notify you of the following status changes:

  • queued requested Requested: the job’s run has been requested and is being executed.

  • queued requested Queued: the job is waiting for the necessary resources to be executed.

  • spinner Running: the job is up and running.

  • fail Failed: the job has crashed. A failed job can go into an out of memory Out Of Memory (OOM) state, which is an extension of the Failed state. The OOM state can be due to a lack of memory (RAM).

  • stop Stopping: the job is stopping.

  • stop Stopped: the job has stopped running.

  • success Succeeded: the job has been successfully executed.

  • unknown Unknown: the job no longer runs because an error has occurred.

6 – Resources Icon for CPU and RAM resources.
For embedded jobs only.

CPU/GPU and RAM resources are optional and can be specified for optimal execution.

The consumption of your job can be managed by guaranteed resources, that is, the minimum amount of resource requested, and limited resources, that is, the maximum amount of resource that can be consumed.

This works the same way for CPU/GPU and RAM resources, except that for RAM you can choose between GB and MB units of measure.

By default, job resource management is disabled because decisions about resource requests and limits are difficult to make without historical data about resource usage patterns of jobs.

Except for specific requirements, you may not enable this feature and let Saagie automatically assign the appropriate resource requests and limits for your job.

Automatic adjustments can be made to avoid inconsistent configurations. If you try to set a guaranteed value greater than the limit value or, similarly, if you try to set a limit value smaller than the guaranteed value, a note appears to inform you that, depending on the situation, the guaranteed value or the limit value has been adjusted (a).

For GPU resources, the guaranteed and limit values must be equal.

RAM limit adjustment message.

Besides, when the guaranteed value and the limit value are not optimal, a recommendation notification appears with the appropriate values for an optimal configuration (b).

CPU recommendation message.

  • Switching from CPU to GPU resources results in the loss of the current configuration.

  • Modifying CPU/GPU and RAM resources automatically restarts your job.