Job Run Modes

Every run of a Job executes in one of two run modes. The mode is a property of the run, not the Job, so the same Job can run incrementally overnight and fully at the weekend.

Incremental - the standard behaviour and the default everywhere. Loads with High Watermarks pull only rows at or beyond the stored watermark, archives merge as configured, and stages truncate and refill.
Full - Loads ignore their High Watermarks and re-pull the whole source, then advance the stored watermark to the full table's maximum so the next incremental run carries on correctly. Use an occasional Full run as a safety net to be certain nothing has been missed by watermarked loads. Archives with expire logic behave as they always have.

Choosing the mode for a run

Scheduled runs use the Job's Scheduled Run Mode setting on the Job edit page: Incremental (the default) or Full. A Job whose loads must never miss anything can schedule a nightly or weekly Full run this way.
Run Now runs the Job the way its schedule would: the Job's Scheduled Run Mode, which is Incremental unless configured otherwise. Run Now (Options) opens a dialog to override the mode for one run.
API runs pass runMode on POST /Jobs/RunJobNow. Code Configs can do the same through BragiUtil.RunJobNow(jobName, runMode).

The mode of every run is recorded against the run's instances and history, and is echoed in Job Callback payloads as runMode.

Interactions worth knowing

Watermarks are shared. A load column's stored watermark is a single value, whichever Job or mode ran the load. A Full run advances it to the whole table's maximum, which is always safe for the next incremental run.
Overlapping runs. If a run of the Job is already in progress, a new API trigger with a callback attaches to it only when the mode matches; a request for different work is turned away, because the run in progress will not produce what that caller asked for.
Archive expiry marks rows as departed when they are missing from the landing table, which is only meaningful when the load holds the complete source. The archive's Expire Departed Rows setting offers three choices: Off, On every run (for archives fed by full-refresh loads), and On Full runs only (for archives fed by watermarked loads - Incremental runs then merge without expiring, and rows only expire on Full runs). With On every run over a watermarked load, an incremental delta would expire every row it did not carry, so validation warns about the combination.
Stored procedure sourced loads have no watermark, so Full changes nothing for them.

02 October 2026