Parity between the surfaces#
What each surface shows, checked against the sources of main on 2026-09-30. The overview
says why the dashboard is one; this page lists where the four surfaces still differ. It changes
when a gap closes.
What each surface shows#
| Sylius | Magento | Filament | Web profiler | |
|---|---|---|---|---|
| Runs listed | All | The 200 most recent | All | Those seen in one request, plus 20 named in durable_execution at most |
| Backend state | 4 states, 3 of them dated | 3 states, all dated | 4 states, 3 of them dated | None |
| Counters | Per outcome, over the page | Per outcome, over the window | Per outcome, over the page | None |
| Outcome filter | Yes | Yes | Yes | No |
| Workflow name filter | Whole name, where the backend can | Whole name, within the window | Whole name, where the backend can | No |
| Execution id filter | Prefix, where the backend can | Prefix, within the window | Prefix, where the backend can | No |
waiting for a worker |
Line and counter | Line and counter, on the database backend | Line and counter | No |
waiting on |
List and run page | List and run page | List and run page | Run section |
| One line per action | Yes | Yes, plus a journal table | Yes | Yes |
| Hatched queue time | Yes | Yes | On the timeline | Yes |
| Red on the failing event | Yes | Yes | On the timeline | Yes |
| Nexus operations table | Yes | Yes | Yes | Yes |
| Worker presence | Per role on Temporal, “Could not ask” on DBAL, none in memory | Journal and activity on Temporal, none in memory | Workflow and activity on Temporal, “Could not ask” on Illuminate, none in memory | No |
| Payload masking | Folded | Folded | Folded | Folded |
| Languages | English, French | English, French | English, French | English |
Words on screen#
The four surfaces use the same words.
| Word on every surface | |
|---|---|
| Heading for the outcome | Outcome |
| Heading for the recorded history | History |
| Heading for the run id | Execution |
| Heading for the backend’s own run id | Backend run, on the three dashboards |
| Outcome value | Running, Completed, Failed, Cancelled, Continued as new |
Three things stay specific to a surface:
- The Magento run page keeps a Journal table under History, one line per event.
- The profiler adds three states that are not outcomes, since they say where a run stands on the request: Queued (no journal yet), Pending and Cancellation requested.
- The Sylius run card is titled Run details, and its History heading sits above the timeline.
- The profiler shows no backend run id.
Behaviours worth knowing#
- Magento counters. They cover the whole 200-run window and ignore the grid filters.
- Continued as new. Grey on Sylius and Filament, purple in the profiler, uncoloured on Magento.
- Profiler. Only runs dispatched during the request appear, plus those named in the
durable_executionquery parameter. See the profiler page.
See also#
- Sylius, Magento, Filament and the web profiler, one page each