Skip to main content

Job Configuration

Fine-tune your jobs for optimal performance and reliability.

Accessing Job Settings​

  1. Navigate to Jobs
  2. Click on the job you want to configure
  3. Click Edit to modify settings

Configuration Options​

Basic Settings​

Job Name​

The job name cannot be changed after creation. To rename, create a new job and delete the old one.

Group​

The group is fixed at creation and cannot be changed afterward. Jobs sharing the same group are displayed together in the list as a collapsible row.

Docker Image​

Update the image to deploy a new version:

myregistry.com/my-job:v1.0  →  myregistry.com/my-job:v2.0
Image Updates

Changing the image does not affect currently running executions. New executions will use the updated image.

Schedule Settings (CronJob)​

Cron Expression​

Modify the execution schedule using cron syntax:

FieldValuesSpecial Characters
Minute0-59*, /, -
Hour0-23*, /, -
Day of Month1-31*, /, -, L, W
Month1-12*, /, -
Day of Week0-6 (Sun-Sat)*, /, -, L, #

Examples:

ExpressionMeaning
*/15 * * * *Every 15 minutes
0 */2 * * *Every 2 hours
30 4 * * *Daily at 4:30 AM
0 0 * * 0Weekly on Sundays
0 0 1,15 * *1st and 15th of month

Timezone​

Select the timezone for schedule interpretation. Common options:

TimezoneOffsetUse Case
UTC+00:00Server operations, international
Europe/Paris+01:00/+02:00French business hours
America/New_York-05:00/-04:00US Eastern business
Asia/Tokyo+09:00Japanese business hours
Best Practice

Use UTC for infrastructure jobs and local timezones only for business-specific tasks.

Concurrency Policy​

PolicyWhen Previous is RunningBest For
AllowStart new executionIndependent jobs
ForbidSkip this executionPrevent resource contention
ReplaceStop previous, start newAlways run latest

Suspend​

Toggle to pause scheduling:

  • Suspended: No new executions created
  • Active: Normal scheduling resumes

Compute Resources​

Compute Class​

Changing compute class affects the CPU:RAM ratio:

ClassRatioEffect
Eco1:2Budget-friendly, lower performance
Standard1:4Balanced for most workloads
Production1:4Dedicated resources, consistent performance
Prod. Compute1:2Optimized for CPU-bound tasks
Prod. Memory1:8Optimized for memory-bound tasks
ARM1:4Cost-effective ARM architecture

CPU Allocation​

Configure in millicores (mCPU):

ValueEquivalent
100 mCPU0.1 cores
500 mCPU0.5 cores
1000 mCPU1 core
2000 mCPU2 cores

Minimum: 10 mCPU Maximum: Varies by compute class (up to 15000 mCPU for Standard)

Memory Allocation​

Memory is automatically calculated based on CPU and compute class ratio:

Example with Standard class (1:4 ratio):

  • 500 mCPU → 2048 MiB
  • 1000 mCPU → 4096 MiB
  • 2000 mCPU → 8192 MiB

A 15% tolerance is allowed for manual adjustment.

Ephemeral Storage​

Temporary storage available during execution:

RangeUse Case
100-500 MiBSmall scripts, minimal temp files
500-2000 MiBData processing, file conversions
2000-10240 MiBLarge file processing, builds
Ephemeral Storage

This storage is cleared when the job completes. For persistent data, use databases or object storage.

Execution Settings​

Restart Policy​

PolicyBehaviorUse Case
OnFailureRetry container on failureMost jobs
NeverDon't retry, fail immediatelyWhen retries aren't safe

Completions​

Number of successful executions required:

ValueBehavior
1Single execution (default)
NJob completes when N pods succeed

Indexed Jobs: When completions > 1, each pod receives a unique index via JOB_COMPLETION_INDEX environment variable.

Parallelism​

Maximum concurrent pods:

ValueBehavior
1Sequential execution (default)
NUp to N pods run simultaneously

Example: Processing 100 items with parallelism 10 runs up to 10 pods at once.

Backoff Limit​

Maximum retries before marking job as failed:

ValueBehavior
0No retries, fail on first error
6Retry up to 6 times (default)
100Maximum allowed retries

Retry delay increases exponentially (backoff).

Timeout​

Maximum duration (in seconds) an execution may run before Kubernetes kills it. Leave empty for no time limit. The minimum value is 1 second.

On a CronJob update, send null via the API to clear a previously set timeout.

History Limits (CronJob)​

Control how many completed executions are retained:

SettingDefaultPurpose
Successful Jobs History3Debug and audit recent successes
Failed Jobs History1Investigate recent failures
History Management

Keep enough history to debug issues, but not so much that it clutters your view.

Container Command​

The container command is configured in Basic Configuration alongside the job name and image. Enter the complete command as you would type it in a terminal:

python script.py
sh -c "echo 'Starting' && python script.py && echo 'Done'"
/app/processor --input=/data --output=/results

Environment & Files​

Environment Variables​

TypeStorageUse Case
PlainVisible in UIConfiguration values
SecretMasked in UICredentials, API keys

Common Variables:

VariableDescription
DATABASE_URLDatabase connection string
API_KEYExternal service authentication
LOG_LEVELLogging verbosity (debug, info, warn, error)
BATCH_SIZEProcessing batch size

Security Context​

SettingDescriptionDefault
Run As UserLinux user IDContainer default
Run As GroupLinux group IDContainer default

Configuration Best Practices​

For Reliability​

  1. Set appropriate backoff limits: Too low fails prematurely, too high delays failure detection
  2. Use Forbid concurrency: Prevent overlapping executions for stateful jobs
  3. Configure timeouts: Set a Timeout to limit maximum runtime

For Performance​

  1. Right-size resources: Start small, increase based on metrics
  2. Use parallelism wisely: More parallelism isn't always faster
  3. Match compute class: CPU-intensive → Prod. Compute, Memory-intensive → Prod. Memory

For Debugging​

  1. Keep sufficient history: At least 1 failed, 3 successful
  2. Log meaningfully: Include timestamps and progress indicators
  3. Use structured logging: JSON format for easier parsing

Service Connections​

The Connections tab lets you wire your job to managed services (PostgreSQL, MariaDB, Valkey, NATS). SailOps injects the credentials as environment variables so your job can connect without manual configuration.

  • CronJobs: you can add, edit, and delete connections at any time. Changes take effect on the next scheduled execution.
  • One-time Jobs: connections are read-only after creation because the pod template is immutable.

See Service Connections for alias conventions, access levels, and the full list of injected variables.

Viewing Configuration​

Overview Tab​

Shows current configuration summary:

  • Job type and status
  • Schedule (for CronJobs)
  • Resource allocation
  • Next/last execution times

Configuration Tab​

Detailed view of all settings:

  • Image and command
  • Environment variables
  • Resource limits
  • Execution parameters

Connections Tab​

Lists active service connections with their target, alias, access level, and creation date. On CronJobs you can manage connections directly from this tab.