Back to the changelog

• Improvement

  Late results respect forced transitions

  After a skip or forced transition, a script or AI task still running cannot overwrite case data or close a new execution of the same task. New attempts stay distinct; an external call already sent may still finish.

• Improvement

  Flow events protected even when features are off

  Existing events with a name reserved to a flow are recognized as engine events when you synchronize the flow, even if the corresponding feature is off. Descriptions and subscriptions are preserved without creating unused events.

• Integration

  Events show actual deliveries

  An event stays in progress while deliveries remain to be completed or retried; it distinguishes successful deliveries, terminal failures and skipped sends. The summary remains available after the attempt log expires. Historical outcomes that cannot be verified are clearly marked; subscriber counters show successful or failed attempts.

• Improvement

  Event task failures in history

  If an Event task uses a reserved event, a missing reference or an invalid template, history shows the reason together with the cause and the affected task. A failed task closure after the event was raised is also identified clearly, helping prevent an unintended resend.