Back to the changelog

• Feature

  Map lifecycle: versions and publishing

  Each map now has a publish status — Draft / Published / Archived — shown with the same coloured badge as flows (green when published, grey when draft, amber when archived), both in the list and in the designer header. Create new versions while keeping history (a clickable version badge opens the list), add an optional version note to document changes, and compare two versions with an automatic diff of added/removed/renamed nodes and edges.

• Feature

  Proactive map health + in-app notifications

  The map no longer breaks silently. Until now the check only ran with the designer open; now, when you change a flow’s activation, publishing or archiving, the maps that reference it are re-checked automatically. A health badge in the list shows errors and warnings without opening the map, and an in-app notification bell alerts you when a change breaks a map — opening it from the notification takes you straight to Diagnostics. Notifications are kept for 90 days.

• Feature

  Map AI analysis, now autonomous

  From the Diagnostics cockpit an “AI analysis” button (premium) generates a reading of the map based only on aggregated data (health, activity, metrics) — never item contents — with copy-to-clipboard. Per map you can enable automatic analysis on alerts: when health degrades, the notification is enriched with the AI analysis and — if you configure an alert flow — an item is opened automatically in that flow, fail-open (the alert is never lost) and deduplicated (one alert per map). Configure it from the map settings, choosing a published alert flow; off by default — no surprise AI spend.

• Design

  Publish-status badge on maps

  The map publish status uses the exact same visual language as flows (green / grey / amber), in both the list and the designer — nothing new to learn.