Back to the changelog

v0.99.10

October 23, 2026

Safer events in the Designer: no publishing toward missing events, invalid payloads without useless retries, warnings when a copy listens to the same events; no AI-generated description unless you ask for it.

  • Improvement

    Missing events stopped before publishing

    If an "Event" task names an event that does not exist, the Designer flags it right under the name and publishing stops with a clear message, instead of failing cases one by one. The match is exact: different capitalisation counts as a different event. Events written as dynamic expressions are not checked.

  • Improvement

    Invalid event payload: clear failure, no useless retries

    When an "Event" task produces data that does not match the event schema, the task fails right away naming the field and the violated rule (never the values), with no automatic retries that would fail the same way. Once the data is fixed, "Retry" runs it again.

  • Improvement

    Warning when a copy listens to the same events

    Importing or duplicating a flow that starts from an event creates a copy listening to the same event: that is intended, but now it is said. The import preview, duplication and publishing warn when another active flow starts with the same events, so you can decide whether that is really what you want. The warning appears at every publish as long as the two flows share the start.

  • Improvement

    AI description only on request

    The flow Designer and the Process Map no longer generate the description with AI on their own at the first save. If the description is empty a discreet hint appears, and the "Generate with AI" button does the job when you decide.

  • Improvement

    Creating flows with the same name at the same time

    Two people creating flows with equivalent names at the same moment both get their flow, with a suffix on the second one's code, instead of a duplicate-code error.