v0.83.4
August 17, 2026
More reliable events, clearer rules. The "deadline first, then the event" rule now covers every delivery scenario, event-linked actions are thoroughly checked before going live, and SLA durations respect a uniform maximum limit.
-
Improvement
Even more reliable event delivery
When an event arrives after a deadline has already passed, FlowSharp applies the timeout first and then delivers the event to the new phase — now also when only the destination phase is listening. No event is lost or delivered to the wrong phase in this scenario anymore.
-
Improvement
Event actions thoroughly checked
Actions linked to event subscriptions (transition, notify, data update) are now validated with closed rules on import, save, and publish: a malformed configuration is flagged immediately with a clear message, instead of being silently ignored at runtime. In exported files, transitions use stable references, checked against the process's allowed transitions.
-
Improvement
Clear limits on SLA durations
SLA durations now respect the same maximum cap as the product's other durations (366 days), across all surfaces: import, settings, editor, and publish. A dynamic value that resolves out of range is treated as an unconfigured SLA, never as an unreachable deadline.