Lex App v2.0.0rc97
Lex App v2.0.0rc97
Release Notes
This release improves the reliability of Lex App calculation execution, especially around asynchronous work, worker lifecycle, and calculation state transitions.
The practical result is a more trustworthy calculation pipeline for long-running business models where users need clear outcomes rather than ambiguous pending or failed states.
This release improves the audit and calculation-log path so operational records are easier to trust during calculations, imports, and background processing.
This release improves packaging, dependency, container, or runtime configuration reliability.
Changelog
Added
- Backend support for more explicit calculation execution and recovery flows where applicable.
Changed
- Calculation state transitions are handled more consistently across synchronous, asynchronous, and nested execution paths.
- Audit and calculation-log records are finalized more consistently around initial data, calculations, and background work.
- Packaging, dependency, image, or runtime defaults were adjusted for more reliable installation and deployment.
Fixed
- Reduced ambiguous calculation outcomes caused by worker shutdown, callback handling, deadlocks, or dispatch timing.
- Reduced cases where logs or audit statuses could be missing, premature, or hard to interpret.
- Reduced environment-specific packaging failures around generated files, package contents, or dependency resolution.
Improved
- Long-running calculations are easier to supervise and recover after runtime interruption.
- Operational traceability is stronger for administrators investigating calculation and data-change outcomes.
Maintenance
- Kept the distributable backend package aligned with the current v2 runtime expectations.
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.
- Rebuild application images or virtual environments so dependency and packaging changes are actually used.
