This is a Long-Term Support (LTS) maintenance release focusing on bug fixes and stability improvements. Upgrades from 5.1.5 → 5.1.6 are non-breaking and fully compatible.
Release Highlight
Maintenance Release: FlowX.AI 5.1.6 delivers bug fixes and stability improvements:
- Multiple React and Angular renderer fixes for modals, sliders, buttons, and accessibility
- Data mappers autocomplete fix for values not loading
- Process engine fix for advancing getting stuck on pod crash with multiple partition events
- Kafka health check fix for reporting UP despite consumer DNS failure
- New health indicator for runtime MongoDB connection
- Connection leak fix in application-manager export/import operations
- Improved retry mechanism with configurable exponential backoff
- Security patches and dependency upgrades
- No breaking changes — fully compatible upgrade from 5.1.5
What’s new? 🆕
- Highlights
- Info
FlowX.AI 5.1.6 delivers bug fixes and stability improvements across the platform.🐛 Bug Fixes — Renderer, process engine, and application manager fixes🔧 Platform Improvements — Retry mechanism enhancements and security patches
Bug Fixes
Bug Fixes
- Renderer fixes (React)
- Renderer fixes (Angular + React)
- Process engine fixes
- Application manager fixes
Issues resolved in the React renderer:
Clear icon present and clickable on disabled input/textarea
Clear icon present and clickable on disabled input/textarea
Summary:When an input or textarea component was disabled, the clear icon was still visible and clickable. The clear icon is now hidden and non-interactive on disabled components.
Options list not shown when selectors are inside modal
Options list not shown when selectors are inside modal
Summary:When select or multiselect components were placed inside a modal, the options list was not displayed when opened. Selector dropdowns now render correctly within modal contexts.
Datepicker calendar shown behind modal
Datepicker calendar shown behind modal
Summary:When a datepicker was placed inside a modal, the calendar popup appeared behind the modal overlay. The datepicker calendar now renders above the modal with correct z-index stacking.
Slider min/max value not set when loading a screen
Slider min/max value not set when loading a screen
Summary:When a slider shared a process data key with an input, or when slider min/max values depended on computed values from another slider, the min/max values were not set on load. Slider initialization now correctly applies min/max values and computed dependencies.
Slider default value not set with multiple sliders on same page
Slider default value not set with multiple sliders on same page
Summary:When multiple sliders were present on the same page, some sliders did not receive their default values, especially when no explicit null value was set in the data store. Default value initialization now works correctly for all sliders on a page.
Task management assignee clear icon clickable when disabled
Task management assignee clear icon clickable when disabled
Summary:In the task management view, the assignee field’s clear icon was visible and clickable even when the field was disabled (non-editable). The clear icon is now hidden when the assignee field cannot be edited.
Input, select, datepicker, textarea, and table filters have incorrect inner outline
Input, select, datepicker, textarea, and table filters have incorrect inner outline
Summary:Multiple form components displayed an incorrect inner outline styling. The outline now only appears during keyboard navigation, following proper accessibility patterns.
Data mappers autocomplete values not loading
Data mappers autocomplete values not loading
Summary:Data mapper autocomplete suggestions were not loading values in certain configurations. Autocomplete now correctly fetches and displays available values.
Platform Improvements
Platform Improvements
- Process engine
- Other improvements
Configurable retry mechanism with exponential backoff
Configurable retry mechanism with exponential backoff
Summary:The retry mechanism for optimistic locking in the process engine now uses an Equal Jitter strategy and supports runtime configuration via environment variables. Previously, the jitter was nullified by the max delay cap, causing retrying threads to collide at the same millisecond.New environment variables for the
process-engine:| Environment Variable | Description | Default Value |
|---|---|---|
FLOWX_RETRY_MAX_RETRIES | Maximum retry attempts (total = max + 1 including initial) | 9 |
FLOWX_RETRY_BASE_DELAY_MS | Initial backoff delay in milliseconds | 10 |
FLOWX_RETRY_MAX_DELAY_MS | Maximum backoff delay cap in milliseconds | 200 |