Back to the changelog

• Security

  Nested data is never silently lost

  Saving item data with deep structures works normally when the write covers every existing key; a change that would erase deep values not mentioned is instead rejected with an explicit error listing the paths involved. Previously the loss could happen without any signal.

• Security

  Gate on legacy AI configuration

  A never-published flow family with an AI task or status still on the legacy configuration is stopped at publish with a dedicated error pointing to the migration: System prompt + User prompt, or an Assistant. This also applies to flows imported from other installations (import always succeeds: it is the first publish that asks for the migration). Already-published flows are untouched, and a non-blocking designer hint flags legacy configuration wherever it appears.

• Improvement

  The portable document carries title and costs

  Title template, AI title, cost type, cost per minute and budget minutes now travel on every path: export and import, duplication, new version, fork and templates. Documents exported in the past import exactly as before.

• Improvement

  Truthful responses and strict inputs

  Duplicating a flow now responds immediately with the real state of event bindings (previously a re-read was needed to see the true values), with a warning explaining that event definitions are shared with the original. And numeric inputs — retry attempts, delays, effort — reject invalid types and values with a clear error instead of silently converting them.

• Improvement

  Titles always fresh and emoji-proof

  Changing an item's entity reference recalculates the title immediately, in the same operation. And long-title truncation no longer splits emoji or composed characters: no more corrupted symbols at the end of a title.

• Improvement

  Unambiguous field paths

  Declaring a plain field and one of its sub-fields (such as "contact" and "contact.email") in the same flow is now rejected with an error pointing at both conflicting paths — in the field registry, on import and at publish. Existing flows remain readable.

• Improvement

  Data editor safe with deep structures

  Opening, editing or copying item data with very deep structures can no longer break the page: past the display limit an accessible notice appears and the value stays intact.