Back to the changelog

• Improvement

  After a wait, the case no longer gets stuck

  When a flow runs several tasks in sequence and one of them is a Wait (or a failed task you retry), the final evaluation that decides where the case goes now always has an owner: it is not lost and does not run twice, even under load. If you retry a task, the following ones that already started are not restarted. Cases already stuck before the update do not recover on their own: just use "Change state".

• Improvement

  More precise deadlines

  A timeout applies only to the visit of the phase it was calculated for: if the case leaves and re-enters the same phase, or the deadline changes, it does not expire by mistake. The expiry event is published only when the deadline really applies, at the same moment as the move: whoever receives it finds the case already in the destination phase.

• Improvement

  Data changed during an automatic evaluation

  If a case's data changes while the rules of an automatic phase are evaluating it, FlowSharp evaluates again with the new data instead of stopping. The number of attempts is limited (only once on AI phases, to avoid repeating the call): at the limit the case stays in the phase with a history line ("Evaluation superseded by data", or "Re-evaluation stopped by an error") and waits for the next change.

• Improvement

  Loops between flows linked by events

  When two flows exchange request and reply through events, publishing warns you if the exchange might never end (a missing iteration limit, or one set to 0, counts as no limit). The warning blocks nothing. A flow started by a "Sub-flow" task also counts toward loop detection, and automatic exchanges stop after ten consecutive starts.

• Feature

  Event subscribers: Connector and readable emails

  Event subscribers can now be Email, Webhook or Connector: the Connector reuses the ones already set up in Settings (with a 30-second limit) and you cannot delete a connector while a subscriber uses it. Emails show the event data in a readable table (you can go back to the technical format), accept placeholders in the subject and body, are sent from your organization's email providers with your branding, and the recipient is checked (up to five addresses). "Send a test" sends a real email. Note: n8n subscribers become Webhooks, while "Custom" ones are deleted with their history; this cannot be undone.

• Feature

  "New event" in four steps

  Creating an event is now a guided procedure: Identity, Payload schema, Who can raise the event and Start these flows. You can press "Create event" from the first step as soon as the key is valid, and the window always fits the screen, with title and buttons visible. When the event is created its card opens and the list filters are cleared, so you see it right away.

• Improvement

  Cases already started are protected

  A case that has already left the initial phase can no longer be deleted or linked to another entity, even if it went back to the initial phase; the same applies to deletions requested for privacy, which treats it as work in progress. The Delete button disappears accordingly. This also applies to cases that went back to the initial phase before this update.

• Improvement

  Stricter checks on folders, notifications and data

  Deleting or moving a folder while someone works on the same flows no longer produces generic errors or inconsistent folders. A notification policy already used as a contact by published flows can no longer receive in-app steps or go back to "for users": the message lists the flows involved. A title that is not text (for example a number) is rejected with a clear error, and so is a data update that wraps everything in a "data" envelope when the flow has no such field.

• Design

  Codes on Management entries

  Every Management entry has a short code (A1…D1) with a colour per group, visible in the menu, on the home, in the section title and in the ⌘K search, where you can also search by code: handy to say "open B14" without ambiguity.

• Design

  "Initiatives" becomes a page of its own

  Initiatives now have their own page in the main menu, with the standard header and the same content as before; Management keeps a shortcut and old links keep working.

• Design

  Uniform look across Management, Profile, Dashboard and portal

  Buttons, fields, tables, notices and dialogs in Data flows, Breach register, Data subject rights, Profile, OAuth consent, MCP keys, data rectification, case conversations and the participant portal now follow the same style, in dark mode too. In the Dashboard the flow panel shows one entry per line. Conversational Profiles show the "persona", "signature" and "tone" placeholders in the prompt preview, with a note on what is replaced during the conversation.

• Improvement

  Data flow inventory without duplicates

  In the data flow inventory, repeated Webhooks and alert steps appear once, with a counter (×N), and archived versions are no longer counted.