Skip to main content

Run history

Every run of a job — scheduled, manual, called by another job, or missed — is recorded with its steps and its log.

At a glance​

Job RunsEvery run, newest first⌕ Search a job, a user, an error…All jobs ▾Last 7 days ▾liveAll 214RUNNING 1FAILED 6SUCCEEDED 205MISSED 2Today · 3 runsRUNNING10:42nomasx1-collect-allapps_id 2👤 j.martin1 min 12 sSUCCEEDED10:15nomasx1-collect-allapps_id 1👤 j.martin4 min 2 s48 210FAILED02:00nomajde-daily-sync⏱ Schedule18 sORA-12170: TNS connect timeoutYesterday · 1 runSUCCEEDED08:00crm-daily-pipeline⏱ Schedule6 s12Search and filtersjob, period — keptState chipswith their countsRuns by dayclick a run to open itLiverefreshed while a run goesParametersthe application of the runProgresssteps done / total

The Job Runs page​

Operations → Job Runs, in the Nomaflow menu, lists every run, newest first.

ElementUse
SearchA job, a user, an error message.
All jobsOne job only.
PeriodLast 24 hours, Last 7 days (the default), Last 30 days, All time.
State chipsAll, then each state present with its count — RUNNING, QUEUED, FAILED, SUCCEEDED, CANCELED, MISSED. A click keeps that state only; a second click clears it.

The filters are kept in the browser. The runs are grouped by day — Today, Yesterday, then the date — and each line shows:

  • the state and the start time;
  • the job and the parameters of the run: for a job run per application, the application it ran for;
  • what started it: the schedule, a user, or the job that called it;
  • the duration — counting while the run goes, with a bar of the steps done —, the rows affected, and under a failed run its error.

While a run is going, the page refreshes itself (live). A click on a line opens the run's detail; Show more loads the older runs. The detail of a run is also reached from the last-run state on the Jobs page and from the link of a notification.

Run states​

StateMeaning
QUEUEDAccepted, waiting to start.
RUNNINGIn progress.
SUCCEEDEDEvery step succeeded or was skipped on purpose.
FAILEDA step failed after its retries. The following steps are recorded CANCELED with skipped: earlier step failed.
CANCELEDCancelled by an operator or by a timeout.
MISSEDA scheduled time at which the job did not run — see Missed schedules.

A run interrupted by a server restart is closed as failed with abandoned: process restart during run when the server starts again.

The Run detail page​

The page refreshes itself every two seconds while the run is in progress (live).

PartContent
SummaryJob, Trigger (scheduled or manual, and who started it — a user name, or call_job:<job>@<run> for a job called by another), Started, Finished, Rows affected.
Run with parametersShown when the run was started with overrides: the values chosen for this run (shared parameters, step arguments, skipped steps, log level).
StepsOne row per step: #, name, Type, Attempt, State, Error. A file_load step also shows N read · N inserted · N rejected, the file uploaded for this run — a click downloads it again — and, if needed, Rejected rows (csv).
LogThe lines written during the run, at the run's log level. Follow keeps the newest lines in view (Pause stops it); Download saves the whole log.

The log keeps the last 5,000 lines of a run.

How long runs are kept​

The Run history retention panel of the Jobs page deletes old runs with their steps and logs: by default runs older than 30 days, keeping at most 100 runs per job, checked every 60 minutes. See Administration.