Back to the changelog

• Security

  Extension linking with confirmed delivery

  The browser extension link becomes active only after the extension confirms it saved the credentials and you confirm from the web page — a tab closed halfway no longer leaves usable tokens around: only an attempt that expires by itself in 5 minutes. Existing links keep working with no action needed.

• Security

  The event log respects visibility

  The detail of an item-generated event can be read only by those with access to the source flow, and system events are reserved for design roles. Operators will see a shorter log: nothing is lost, it is a matter of who can read what.

• Improvement

  Event tasks always tell the truth

  An Event task can no longer show as "completed" without the event actually going out: errors mark the task as failed with the reason, success records the correlation, and a double execution never produces duplicate events.

• Improvement

  The extension starts flows as a human gesture

  Starting a flow from the extension now follows manual-start rules, roles included: you can have a flow startable by people via the extension but closed to API keys. Starts count in KPIs as human activity.

• Improvement

  Task detail identical from every door

  "Do It" and the phase Guide also work when opening a task from the Tasks page or a direct link; the panel shows the flow link and refreshes if the item changes while open. And the data editor shows business data only — system metadata is readable separately and save errors explain the real cause.

• Improvement

  A more honest Designer and organization profile

  Flow-save warnings (like a non-existent Library slug) now stay visible in a dedicated panel until you resolve them. And the organization profile validates emails, website and Italian fiscal codes in form — with no new required fields and without blocking historical data.