September 3, 2026 — Tracking, rules in shadow mode and field inheritance

This update brings tracking, which measures the time each entity spends in each value of a field, the publishing of rule versions in shadow mode, and control over field inheritance between events.

Tracking

A discrete field can be marked as trackable, and the platform starts recording how long each entity stays in each of its values: the duration of an order in pending, the time an account spends under block. Tracking provisions two derived fields, available like any other field in metrics, filters and rules.

Over them you can measure both the periods that already closed, with the ordinary aggregations, and the open periods, which count the entities still held in a value and the age of the oldest one. A scope by open time separates a stuck process from a merely slow entity, and the monitor alerts when the buildup goes past what is expected. See Tracking and Fields.

Rules in shadow mode

A rule version can be published in observation (shadow): it runs in parallel with the active version, over the same real events, without deciding anything. You choose which outputs to track, and each one is written to the same event, next to the value the active version wrote, which lets you compare the two with the Explore filters, the Metrics and the Dashboards you already use. An inactive version can also be observed, to answer whether it really was the one that changed the behavior. See Versioning.

Field inheritance

Each field now defines whether it is inherited by later posts under the same id. Turn Inheritance on for the fields that describe the entity and arrive only in the first post, such as the customer or the merchant, and leave it off for the ones that hold only for that post, such as the step or the response code of the attempt. See Inheritance between events under the same id.

Analyses: cell with no trigger

A cell can use the No trigger signal, which maintains the window and exposes the measured value without ever firing. It is how a number is carried from the window to the event, such as an order’s attempt counter, leaving the decision to a rule condition. The cell editor was reorganized into Identity, Window, Measure and Trigger, with ready-made examples, and the cell list can be reordered by dragging. See Analyses.

Other improvements

• Metrics: the chart now has one vertical axis per unit, labelled in that unit, so a duration is never read as a bare number nor shares a scale with a count. See Chart.
• Fields: new Duration display, which presents an integer as 3.5s or 2d 1h; fields managed by the platform now accept changes to name and description. See Fields.
• Explore: filters over duration fields accept the value typed as time (30s, 1h 30m, 2d), and a saved search can be overwritten with the current settings or deleted.
• Export: the file is now delivered compressed (.csv.gz) and carries its own description, with period, filters and the list of columns. See Export.
• Rules: a history of the actions taken on each version, highlighting of expressions as they are written, and the event identifier available as $id in conditions and analyses.
• Event types: the panel shows when the last event was received.
• Connected agent (MCP): new tools for the agent to consult monitors and a specific permission to let it edit a field’s name and description. The feature now has documentation of its own in Connect agent.