Changelog

Lex App v2.0.0rc132

Lex App v2.0.0rc132

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 refines how Lex App records lifecycle and bitemporal history around model changes.

This release improves the audit and calculation-log path so operational records are easier to trust during calculations, imports, and background processing.

Changelog

Added

  • Backend support for more explicit calculation execution and recovery flows where applicable.
  • Additional setup and initialization support for project bootstrap and environment-specific configuration.

Changed

  • 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.
  • Audit and calculation-log records are finalized more consistently around initial data, calculations, and background work.

Fixed

  • 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.
  • Reduced cases where logs or audit statuses could be missing, premature, or hard to interpret.

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.
  • Regenerate or review generated project setup files if the project relies on Lex App initialization commands.