Back to the changelog

v0.97.5

October 14, 2026

Confidential data protected everywhere, instant analytics even at large volumes, sample cases ready to work on.

  • Security

    Better-protected credentials and personal data

    Connector credentials, outgoing webhook addresses and headers, and email text no longer stay in clear text in work queues or in the database: they are read and decrypted only when sending. If you revoke a connector or a recipient, nothing is sent with the old data any more. Logs no longer record request parameters, and sign-in attempts with a non-existent address no longer keep it in clear text. Sign-in answers with the same timing for existing and non-existent accounts. Emails that fail because of a temporary mail server problem are retried, and those that fail for good are visible in the system status.

  • Security

    A more complete Data Shield

    Confidential fields stay protected even when a Sub-flow copies their content with {{json …}}: the child case field is created as confidential and the Designer warns you. Sending a masked value back to FlowSharp, in any form FlowSharp produced it, no longer erases the original data. For fields inside a list you can protect the whole list or a specific item; a configuration the system cannot apply is rejected with an explanation, and a field inside a list masks the whole list instead of staying visible. Publishing warnings on Webhooks and Events flag only data that would really be sent in clear text.

  • Improvement

    Instant analytics and summaries

    Flow analytics, version comparison, the event summary and automation indicators are computed directly in the database: on one hundred thousand cases a flow's detail goes from about three and a half seconds to under one second. Analytics without a chosen period show the last 90 days, and say so. Searching case data stays fast even on very large archives and tells you when it is worth refining.

  • Feature

    Sample cases ready to work on

    Cases created from demo data, scenarios and imports with sample data arrive with their tasks ready and assigned to whoever loaded them, so you can move them forward right away. A sample case's automations are simulated: no email, webhook, AI call or event is sent from test data. Sample cases loaded earlier are also unlocked on their first status change.

  • Improvement

    Reliable import and export

    A flow with a Sub-flow is exported without internal references: on import the child flow is found by code, and if it is missing you get a warning instead of an error. The Solution import preview shows exactly what the import will do, including errors and adjusted codes, and is also available through the API. Exports and templates created from flows with settings from earlier versions re-import without intervention, with a note on what was fixed. The Flows list loads lighter.

  • Improvement

    More consistent events and cases

    Event deliveries no longer stay "Pending" forever: those that can no longer complete are closed with a clear reason. An action that updates a field from an event lacking that field no longer erases the existing value. The AI summary is not generated for cases that never started. A rejected transition no longer starts a scheduled case early. Correcting the outcome of a completed task accepts only the expected outcomes.

  • Improvement

    Fixes and polish

    Map pages no longer show errors when the plan does not include Saving. Generating demo data without an AI provider explains what to configure. After signing in again, the support banner no longer stays stuck. Automated task logs report the reason for an error. The license portal recognises the official demo builds.