Lex App v2.0.0rc160
Lex App v2.0.0rc160
Release Notes
This release makes calculation cancellation behave more like a coordinated system event. Cancellation is treated across active calculation state, worker execution, and related child work instead of being handled as a narrow local flag.
For users, cancelled work is less likely to keep running in the background or leave follow-on calculations in a misleading state.
This release improves the reliability of Lex App calculation execution, especially around asynchronous work, worker lifecycle, and calculation state transitions.
This release refines how Lex App records lifecycle and bitemporal history around model changes.
Changelog
Added
- Cluster-aware cancellation tracking for calculation work that spans workers or dependent tasks.
- Backend support for more explicit calculation execution and recovery flows where applicable.
Changed
- Cancellation now propagates more deliberately through active calculation state and nested execution paths.
- Calculation state transitions are handled more consistently across synchronous, asynchronous, and nested execution paths.
- History and lifecycle timestamps are aligned more closely with business-relevant model changes.
Fixed
- Reduced the risk of cancelled calculations continuing silently or leaving child work in an inconsistent state.
- Reduced ambiguous calculation outcomes caused by worker shutdown, callback handling, deadlocks, or dispatch timing.
- Reduced noise in history caused by framework-driven calculation or setup activity.
Improved
- Long-running calculations are easier to supervise and recover after runtime interruption.
- Bitemporal records are more dependable for audit, reporting, and as-of analysis.
Upgrade Impact
- Apply database migrations before running history, audit, or calculation-heavy workflows after upgrading.
- Restart application workers and schedulers so calculation execution, cancellation, and recovery behavior use the new backend code.
