schedule_simple_nodups

Trigger a repaired outcome when a job should be run (avoid running twice).

⚙️ Compatible targets: Linux

Parameters

Name	Documentation
job_id	A string to identify this job. This parameter is required.
agent_periodicity	Agent run interval (in minutes). This parameter is required.
max_execution_delay_minutes	On how many minutes you want to spread the job. This parameter is required.
max_execution_delay_hours	On how many hours you want to spread the job. This parameter is required.
start_on_minutes	At which minute should be the first run. This parameter is required.
start_on_hours	At which hour should be the first run. This parameter is required.
start_on_day_of_week	At which day of week should be the first run. This parameter is required.
periodicity_minutes	Desired job run interval (in minutes). This parameter is required.
periodicity_hours	Desired job run interval (in hours). This parameter is required.
periodicity_days	Desired job run interval (in days). This parameter is required.

Outcome conditions

You need to replace ${job_id} with its actual canonified value.

✅ Ok: schedule_simple_${job_id}_ok
- ☑️ Already compliant: schedule_simple_${job_id}_kept
- 🟨 Repaired: schedule_simple_${job_id}_repaired
❌ Error: schedule_simple_${job_id}_error

Example

method: schedule_simple_nodups
params:
  periodicity_hours: VALUE
  start_on_minutes: VALUE
  start_on_day_of_week: VALUE
  start_on_hours: VALUE
  periodicity_days: VALUE
  max_execution_delay_minutes: VALUE
  job_id: VALUE
  periodicity_minutes: VALUE
  agent_periodicity: VALUE
  max_execution_delay_hours: VALUE

Documentation

This bundle will define a condition schedule_simple_${job_id}_{kept,repaired,not_ok,ok,reached}

_ok or _kept for when there is nothing to do
_repaired if the job should run
_not_ok and _reached have their usual meaning

If the agent is run twice (for example from a manual run), the jo is run only once. However if the agent run is skipped during the period, the job is never run.