Back to the changelog

• Feature

  New version without losing work

  Editing a published flow is no longer a dead end. As soon as you touch the canvas a banner tells you, the button becomes **"Create new version"** and one click creates the draft with all your changes — design and activation settings together, in a single operation: everything lands, or nothing is created. The published version stays live and untouched, and a double click or a retry after a timeout never creates two drafts.

• Security

  Sensitive data follows the data

  When a child flow receives data from its parent, sensitivity travels with each item: no blanket marking, no sensitive paths silently lost. And share links are now frozen at creation — whoever holds the link sees that moment's snapshot, not a live window onto your design — with tokens, headers and sensitive parameters always redacted.

• Improvement

  Visible failures, reliable outcomes

  Event rules that keep failing land in a browsable dead-letter with history and reason, archivable and never "immortal". If the engine degrades or recovers, an alert goes out. And every task outcome only counts for the run it belongs to: a late result never overwrites a newer run. Violated deadlines stay on record, and timeouts written with variables recompute when the variable arrives.

• Feature

  Events: guided activation and observable delivery

  The Events page is now complete: configure definitions, see which flows and statuses actually use them, and activate flows with a preview of what will happen. Every publication has a per-recipient outcome — delivered, skipped, failed — with dedicated analytics, and external systems can safely retry a publication with an idempotency key.

• Improvement

  Operational views that tell the truth

  The kanban shows where items actually land when a WIP limit redirects them. Calendars load the period you are looking at, with stable sorting. Items and tasks only suggest real assignees. SOP guides get search and pagination, flow actions are gathered into a tidy menu (keyboard included), and views adapt better to narrow screens.

• Improvement

  Maps follow versions

  Process map nodes follow the flow family: when you publish a new version, the map automatically points to it. Unwiring an edge is an atomic operation, and the real state of the wiring is visible on the map.