A run is one execution of a job, from its trigger to its last action. Each time a job starts, the platform records the run, and the admin lists it as a batch under Customization › Orchestration › Batch Logs. Job run, job batch and batch are the same thing; older pages say hook batch.

  1. Its status says how it ended: success, error, or skipped when a condition or a Stop ended it on purpose. While it is still going it shows initialized, running or waiting.
  2. Its actions are listed one row each, in the order they ran, with what each one output. A loop adds a row for every element.
  3. Whether it is kept depends on the job's Batch persistence. With never or success, a failed run leaves no log at all.

Reading a failed run in the right order is in Debug a job run that failed halfway.