v0.43.0
July 11, 2026
The interface comes alive: items, tasks and notifications update in real time, with no page reload. Whoever is looking at an item sees transitions, tasks and history move on their own while the engine works; the bell rings instantly; the Chrome extension cockpit refreshes as soon as the entity changes. And tasks become first-class events: completion and failure can now drive notifications and automations.
-
Feature
The page moves on its own
Live item detail. Status transitions, tasks completing (including the asynchronous n8n and worker ones), history and data: everything shows up within a second, no manual refresh. It works for every channel: human action, automatic rule, event, timeout, WIP, SLA. Instant notifications: in-app notifications reach the bell the moment they are born (they could previously wait up to a minute), filtered for the right recipient. Real-time extension cockpit: the Chrome extension side panel refreshes on its own when the displayed item changes — over a secure connection that honors token revocation.
-
Improvement
Robust by construction
If the connection drops, you won’t notice. The UI automatically degrades to the usual polling (no regression possible) and realigns itself on recovery. With real time active, polling thins out and lightens the server. Total isolation: each tenant only sees its own signals; only identifiers travel on the channel, never business data. Context switches (SuperAdmin impersonation) re-attach the stream to the right tenant. No wasted streams: background tabs close the connection and reopen it on return; event bursts are coalesced so the server is never flooded.
-
Feature
Tasks become events
Hookable task-completed and task-failed. Every status with tasks now exposes two new registered events (like the timeout/WIP/SLA runtime events): they can be selected for notifications and automations — for example "alert me when a task fails in Review". They fire for automatic, AI and webhook tasks and for manual completions. For environments with existing flows, the events are registered with the usual admin backfill (POST /admin/backfill-runtime-events).