Tutorial · Communication

Review automation history

Open run history, filter outcomes, and move from a run to its workflow without changing the schedule.

5 minVerified on 21 Sept 2026Leaders and office staffAvailable
1Step 1 of 5 · 1 min

Open Workflows

Open Workflows and select Run history in the header. The page also has Recent runs, limited to the six newest rows, with See all. The recent-runs panel is hidden when no runs exist.

Reviewing history is read-only. It does not start, repeat, or edit a workflow.

Fig. 1Run history opens the general list of recorded runs.
2Step 2 of 5 · 1 min

Read history rows

The general history loads up to one hundred recent runs for the active scope. Each row shows the workflow, an outcome summary, and date or time; an error can also identify the channel and a short message.

Selecting a row opens the workflow detail, not a copy of that individual run. Row outcome summaries currently remain Italian in English mode.

Fig. 2All combines the available published, partial, failed, and manual runs; row summaries retain their current Italian wording.
3Step 3 of 5 · 1 min

Filter the outcome you need

Use Published, Partial, Failed, or Manual. Filtering changes only the loaded list and does not alter stored data.

Manual includes person-triggered runs; Published maps to completed status, Partial retains warnings, and Failed collects errors.

If the filter is empty, return to All and check the active scope.

Fig. 3Failed isolates the Bollettino mensile Facebook error; no new run has started.
4Step 4 of 5 · 1 min

Open the correct detail

Select a row to open its workflow, then choose the Italian Esecuzioni tab. In detail, the controls Tutte, OK, Errori, Parziali, and Manuali filter that workflow’s runs, and the side card summarises the last sixty days.

The detail states that run history is kept for 180 days. Generated PDFs remain available from Bulletins.

5Step 5 of 5 · 1 min

Interpret without rerunning

A completed row can offer PDF when its output contains a bulletin. A failed row offers Risolvi, which displays the stored message; it does not repair the cause automatically.

Do not select Esegui ora during a review: it creates a new manual run and can publish immediately.

What you have achieved

  • You isolated relevant outcomes without changing workflows or schedules.
  • You can open the linked workflow to inspect configuration and the recorded error.