Skip to content

Runs ​

Every time a job runs, on its schedule or because someone started it, it leaves a row on the Runs page. This is where you check that last night's sync finished, how long a report took, or why a job had nothing to do.

Where it lives ​

Open Runs in the sidebar. The page lists runs newest first, with Load more at the bottom for older ones. Each row shows:

ColumnWhat it tells you
JobWhich job ran. Reports and analyses start with "Report:" or "Analysis:".
StatusHow the run ended. See the table below.
StartedHow long ago it started. Hover for the exact time.
DurationHow long it took.
DetailsThe reason a run failed or skipped, or a note from a run that finished. Click it to read the whole message.

Use All job types and All statuses above the table to narrow the list, for example to every failed run of one sync.

What each status means ​

StatusMeaning
RunningThe job is working now.
Success or CompletedThe job finished. The two words mean the same thing.
SkippedThe job ran and stopped without doing anything, and recorded why. Details has the reason.
FailedThe job stopped with an error. Details has the reason.

Two skips you are likely to see:

  • Auto-draft replies, when your workspace only drafts where sources are found and none matched. Details names how many conversations were left without a draft. See Only draft when sources are found.
  • Auto-draft replies, when Allowed inboxes is empty, or names no inbox on any help desk you have connected. Details says which.
  • Close stale conversations, when no inbox is named in Allowed inboxes. Details says exactly that.

A report or an analysis that your plan doesn't include, or that has no connected help desk to read, is marked Skipped with the reason. Not every job that had nothing to do says so: to see what a run actually produced, look at its result, for a report the Recent reports list on Reports.

Failed drafting, report and analysis runs also raise an alert, so you hear about them without opening this page. See Alerts.

When a job leaves no row ​

Auto-draft replies leaves no rows at all until your workspace has a documentation source. Drafting waits for it, and there is nothing to record until then. See Point Overdesk at your docs.

If a job you expected is missing, check Schedules to see whether it is paused, and Jobs to start it by hand.