> ## 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.

# FlowX.AI 5.1.6 Release Notes (LTS)

> Bug fixes, stability improvements, and platform enhancements for the FlowX.AI 5.1.x LTS line.

<Info>
  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.
</Info>

<Card title="Release Highlight" icon="star" iconType="duotone">
  **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
</Card>

***

**What's new? 🆕**

<Tabs>
  <Tab title="Highlights">
    FlowX.AI 5.1.6 delivers bug fixes and stability improvements across the platform.

    🐛 [**Bug Fixes**](#bug-fixes) — Renderer, process engine, and application manager fixes

    🔧 [**Platform Improvements**](#platform-improvements) — Retry mechanism enhancements and security patches

    ***

    ### **Bug Fixes**

    <Card title="Bug Fixes" icon="bug" iconType="duotone">
      <Tabs>
        <Tab title="Renderer fixes (React)">
          Issues resolved in the React renderer:

          <Accordion title="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.
          </Accordion>

          <Accordion title="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.
          </Accordion>

          <Accordion title="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.
          </Accordion>

          <Accordion title="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.
          </Accordion>

          <Accordion title="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.
          </Accordion>

          <Accordion title="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.
          </Accordion>

          <Accordion title="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.
          </Accordion>

          <Accordion title="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.
          </Accordion>
        </Tab>

        <Tab title="Renderer fixes (Angular + React)">
          Issues resolved in both Angular and React renderers:

          <Accordion title="Card height does not update when accordion is collapsed">
            **Summary:**

            When a card component with fixed height contained an accordion, the card height did not update when the accordion was collapsed. Card height now correctly recalculates when accordion state changes.
          </Accordion>

          <Accordion title="Focus outline appears when interacting with card/file preview accordion">
            **Summary:**

            When interacting with a card or file preview component that included an accordion, an unwanted focus outline appeared. The focus outline is now only displayed during keyboard navigation.
          </Accordion>

          <Accordion title="Button icon not correctly rendered">
            **Summary:**

            When a button was configured with a right-aligned icon, fill width, and right-aligned typography, the icon was not aligned with the text, the gap was missing, and text and icon were center-aligned instead of right-aligned. Button icon layout now respects all configured alignment and spacing settings.
          </Accordion>
        </Tab>

        <Tab title="Process engine fixes">
          <Accordion title="Advancing gets stuck when multiple events are available for one partition and pod crashes">
            **Summary:**

            When multiple events were available for the same partition and a pod crashed, only the first event was picked up and the rest remained stuck. Event processing now correctly handles all pending events after a pod recovery.
          </Accordion>

          <Accordion title="Kafka health check reported UP despite consumer DNS failure">
            **Summary:**

            The Kafka health check indicator could report UP even when consumers had DNS resolution failures, masking connectivity issues. Health indicators now correctly reflect the actual state of Kafka consumer connections.
          </Accordion>

          <Accordion title="Health indicator for runtime MongoDB connection">
            **Summary:**

            A new health indicator has been added to monitor the runtime MongoDB connection. This improves observability and allows operators to detect MongoDB connectivity issues through the standard health endpoint.
          </Accordion>
        </Tab>

        <Tab title="Application manager fixes">
          <Accordion title="Theme not imported during build import">
            **Summary:**

            When importing a build that included theme resources, the theme was not correctly imported. Build import now includes theme resources as expected.
          </Accordion>

          <Accordion title="Connection leak in export/import services">
            **Summary:**

            During import/export operations, database connections were held for the entire duration of long-running operations (MinIO file transfers, REST calls, Kafka messaging), which could exhaust the connection pool. Transaction boundaries have been refined so that database connections are only held during actual database operations.
          </Accordion>
        </Tab>
      </Tabs>
    </Card>

    ***

    ### **Platform Improvements**

    <Card title="Platform Improvements" icon="wrench" iconType="duotone">
      <Tabs>
        <Tab title="Process engine">
          <Accordion title="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`         |

            <Tip>
              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.
            </Tip>
          </Accordion>
        </Tab>

        <Tab title="Other improvements">
          <Accordion title="Removed deprecated access rights endpoint">
            **Summary:**

            A deprecated endpoint and its associated test for access rights have been removed from the codebase as they are no longer needed.
          </Accordion>

          <Accordion title="Security patches">
            This release includes security patches across all platform components to address known vulnerabilities.
          </Accordion>
        </Tab>
      </Tabs>
    </Card>

    ***
  </Tab>

  <Tab title="Info">
    ## Additional information

    <Info>
      **Upgrade Compatibility**: FlowX.AI 5.1.6 is fully compatible with 5.1.5. No configuration changes, schema migrations, or data transformations are required.
    </Info>

    ### Compatibility

    <CardGroup cols={2}>
      <Card title="Upgrade Path" icon="arrow-up-right-dots">
        Direct upgrade from 5.1.5 → 5.1.6 with no breaking changes or configuration updates
      </Card>

      <Card title="Component Compatibility" icon="circle-check">
        Compatible with FlowX.AI SDKs (Angular/React/iOS/Android), Designer, and Database 5.1.x
      </Card>
    </CardGroup>

    ### Deployment information

    <Info>
      Standard deployment procedures apply. No special migration steps required for this maintenance release.
    </Info>

    For detailed deployment guidelines, see [Deployment Guidelines v5.1.6](./deployment-guidelines-v5.1.6).

    ### What's next

    **FlowX.AI 5.1.x LTS** will continue to receive maintenance updates focused on:

    * Security patches and vulnerability fixes
    * Stability improvements and bug fixes
    * Performance optimizations
    * Additional renderer enhancements
  </Tab>
</Tabs>