The dashboard in Magento#

To follow the workflows of a store from the Magento admin, install gplanchat/durable-magento (Packages) and open System > Durable processes > Process history. The page is read-only. It is in English or French, following the Interface Locale of the admin account. The texts the core composes, such as the event labels and the waiting on … values, stay in English, as on Sylius and Filament.

Screenshots#

The Magento process history grid: backend state, worker presence, counters per outcome and the list of runs

System > Durable processes > Process history, over eight runs of the bench: four completed, two failed, and two running, one of them suspended on a timer.

The Magento run page of a completed execution, with its History timeline

The run page of order/4244: the execution, the backend run and the outcome, then a History timeline where durable.demo.charge is hatched for the 30 seconds it waited for a worker.

Give access to a role#

The screen has its own ACL resource. In System > Permissions > User Roles, tick Durable processes > Process history on the role’s resources.

What the page offers#

The backend state, dated, and one line per worker role (journal and activity) when Temporal holds the journal (the recorded steps of an execution and their results).
Counters per outcome, over the 200 most recent runs, whatever the grid filters say. On the database backend, a Waiting for a worker count joins them. The grid and the run page show waiting for a worker · 42 s for a run nobody has picked up.
The standard admin grid: paging (20 by default), column controls, and filters on outcome, workflow name, execution id and backend run id. The text filters follow the rule of the other surfaces, among the runs of the window: the whole workflow name, the start of the execution id and of the backend run id, all as typed. A notice states the window when it is full.
A run page, opened from a row: the execution, its backend run, outcome, start and end dates, what it waits on, its Nexus operations, a History timeline and a Journal table with one line per event (kind, phase, action, what happened). See Read a run.

What it does not show#

On the Temporal backend, the grid does not say waiting for a worker: the run list records no pickup time. The window is 200 runs: an older run does not appear, and the counters do not reach it either. See Parity.

Payloads#

A payload unfolds on demand. It is masked by the preference your application declares for Gplanchat\Durable\Observation\PayloadRedactorInterface; the module ships the key-name redactor.