v0.94.2
October 6, 2026
More consistent flow design from agents too.
-
Integration
Automatic correction from agents too
When an agent generates and applies a flow, FlowSharp corrects overlong fields with the same rules as the designer and reports the corrections made. If a value cannot be safely repaired, or an explicit name or code is too long during creation, the agent receives a clear error before saving.
-
Improvement
Design in the AI Call Log
Administrators can filter flow design calls on a dedicated channel, separate from the System One preview. Correction calls are visible too, with the requester, flow when known, tokens, latency and outcome. The level selected on the provider determines whether to keep metadata only or also prompt and response; earlier calls are not reconstructed.
-
Improvement
Event deliveries without indefinite waiting
A delivery that exhausts its attempts without recording a result is closed as failed with a readable reason. The detail retains the reason even if the target or history is no longer available; an already successful delivery stays successful. Earlier entries are not reconstructed.
-
Improvement
Guided recovery of interrupted decisions
Administrators can release a decision left running after a stop, with a reason and acknowledgement of the possible cost. The journal is preserved and the item receives no late results from the previous attempt. The task becomes Failed, allowing Retry to be chosen. The action becomes available after the minimum protection period.