v0.55.0
July 21, 2026
No more "fake success": invalid input is stopped, not swallowed. Malformed JSON, invalid data schemas, subscribers with no destination and wrong WIP limits are now blocked with a clear message. And events get a readable name separate from the technical key.
-
Improvement
Invalid input stopped, not swallowed
In the events console a malformed JSON payload no longer publishes an empty event, and while editing a subscriber an invalid JSON no longer silently resaves the previous configuration: in both cases you now get an error and the save stops. The flow's data schema must also be an object (not a list or a single value) and the WIP limit is validated as you type.
-
Improvement
Subscribers must have a destination
A Webhook subscriber with no URL, an n8n one with no webhook URL, or an Email one with no recipient can no longer be saved as "active" only to fail at runtime: the system rejects it right away explaining what's missing, and requires a valid web address for webhooks.
-
Feature
Events: readable name and stable key
Every event now has a free display name (e.g. Order shipped) alongside a canonical key the system uses for routing (e.g. order.shipped), auto-derived from the name and format-validated. The key stays stable over time, while the shown name can be tweaked when needed. Existing events keep working as before.