Jobs

Jobs automate repeatable liveops tasks. A job can update Live Config, publish selected paths, roll back to a prior publish, or call a webhook.

Trigger types

Trigger	Use it for
Time	Run once or on a cadence
Variable	React to a Live Config path changing
Manual	Keep the job available for one-click operator runs

Job kinds

Kind	What it does
Configuration	Updates Live Config values and can publish
Webhook	Calls an external HTTP endpoint

Configuration value modes

Mode	Example
Static	Set `event.enabled` to `false`
Expression	Set `shop.saleText` from other config values
Publish selected	Publish only approved paths
Rollback to publish	Restore a previous published version

Example: turn off an event

Create a scheduled configuration job:


{
  "name": "End Lucky Weekend",
  "triggerType": "SCHEDULE",
  "targetPath": "event.enabled",
  "valueMode": "STATIC",
  "value": false,
  "publish": true
}

Operator flow:

Open Jobs.
Select Production and the target profile.
Create a configuration job.
Choose Time as the trigger.
Set event.enabled as the target path.
Set the static value to false.
Keep publish enabled.
Preview, save, and verify the scheduled run time.

Example: webhook notification

Use a webhook when an external system needs to know about a liveops action.


{
  "name": "Notify Discord Bridge",
  "triggerType": "MANUAL",
  "method": "POST",
  "url": "https://example.com/liveops/event",
  "body": {
    "game": "Arena Events",
    "event": "Lucky Weekend",
    "state": "started"
  }
}

Conditions

Jobs can include conditions so they only run when the current config matches the expected state.

Examples:

Run only if event.enabled equals true
Run only if maintenance.enabled is truthy
Run inside a schedule window

Safe operation checklist

Before enabling a Production job:

Confirm environment and profile.
Preview or simulate the job.
Confirm whether it publishes immediately.
Add conditions if a repeated run would be risky.
Set retry count only when the job is safe to repeat.