Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.flowx.ai/llms.txt

Use this file to discover all available pages before exploring further.

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? 🆕
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

Issues resolved in the React renderer:
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.
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.
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.
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.
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.
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.
Summary:Multiple form components displayed an incorrect inner outline styling. The outline now only appears during keyboard navigation, following proper accessibility patterns.
Summary:Data mapper autocomplete suggestions were not loading values in certain configurations. Autocomplete now correctly fetches and displays available values.

​
Platform Improvements

Platform Improvements

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 VariableDescriptionDefault Value
FLOWX_RETRY_MAX_RETRIESMaximum retry attempts (total = max + 1 including initial)9
FLOWX_RETRY_BASE_DELAY_MSInitial backoff delay in milliseconds10
FLOWX_RETRY_MAX_DELAY_MSMaximum backoff delay cap in milliseconds200
Default settings give a total retry window of ~1.2 seconds, which covers most transient optimistic lock conflicts. Increase FLOWX_RETRY_MAX_RETRIES or FLOWX_RETRY_MAX_DELAY_MS if you see retry exhaustion under high contention.
Last modified on March 26, 2026