This is a Long-Term Support (LTS) maintenance release focusing on security patches, performance optimizations, bug fixes, and stability improvements. Upgrades from 5.1.2 β 5.1.3 are non-breaking and fully compatible.
Release Highlight
Maintenance Release: FlowX.AI 5.1.3 delivers security patches and significant performance improvements:
- Numerous bug fixes addressing reported and internally identified issues
- Improvements and enhancements to various platform components
- Platform tasks focused on infrastructure and overall stability
- No breaking changes β fully compatible upgrade from 5.1.2
Whatβs new? π
- Highlights
- Info
FlowX.AI 5.1.3 delivers comprehensive security, performance, and stability improvements across the platform.β¨ Improvements and enhancements β AI Platform improvements and enhancements for Data Model generation
β‘ Performance Improvements β Performance improvements and optimizations across platform components and services
π Bug Fixes β Customer-reported and proactive fixes across platform components
π§ Platform Improvements β Infrastructure hardening and dependency updates
β‘ Performance Improvements β Performance improvements and optimizations across platform components and services
π Bug Fixes β Customer-reported and proactive fixes across platform components
π§ Platform Improvements β Infrastructure hardening and dependency updates
Improvements and enhancements
Improvements and enhancements
- AI Platform
Data Model Generation for Tables
Generate Data Model mappings for table components from AI Designer. AI automatically creates array of objects DM keys for tables with type validation and visual feedback.
Data Model Generation for Table Columns
Extended DM generation for text and link elements within table columns, with automatic attribute mapping and support for partial matching.
Performance improvements
Performance improvements
- Overview
- Key optimizations
FlowX.AI 5.1.3 delivers significant performance improvements to the process engine
Optimized Writes
Smart change detection skips unnecessary database writes when param_values unchanged
Reduced DB Calls
N+1 query fixes and batch loading significantly reduce database round trips
Request Caching
Request-scoped caching for frequently accessed runtime configuration
Bug fixes
Bug fixes
- Customer fixes
- Designer fixes
- Renderer fixes
Issues resolved based on customer feedback:
Task Manager View Not Updating
Task Manager View Not Updating
Problem:
When using a view with dataset config where assignee is set to blank, after assigning a task (or self-assigning), the view appeared unchanged. Similarly, when assignee is set to not blank and you unassign a task, the view did not update.Resolution:
Fixed view refresh behavior after assign/unassign operations to properly reflect the updated task state and provide visual feedback to users.
When using a view with dataset config where assignee is set to blank, after assigning a task (or self-assigning), the view appeared unchanged. Similarly, when assignee is set to not blank and you unassign a task, the view did not update.Resolution:
Fixed view refresh behavior after assign/unassign operations to properly reflect the updated task state and provide visual feedback to users.
Forms in Collections - Backend Keys Calculation
Forms in Collections - Backend Keys Calculation
Problem:
When saving data from outside a collection with forms to submit, the backend calculated keys for UUID entries in formsToSubmit. These keys were only partial (relative to the collection array) and could overwrite existing process values.Resolution:
Added a flag on PATCH /actions requests to notify the backend to exclude backend keys calculation for forms in collections UUIDs from formsToSubmit.
When saving data from outside a collection with forms to submit, the backend calculated keys for UUID entries in formsToSubmit. These keys were only partial (relative to the collection array) and could overwrite existing process values.Resolution:
Added a flag on PATCH /actions requests to notify the backend to exclude backend keys calculation for forms in collections UUIDs from formsToSubmit.
Variables Reset on Config Update
Variables Reset on Config Update
Problem:
Updating parameters in the config page caused existing parameters to be replaced with new ones, generating new flowxUuids. This caused variables in database nodes to no longer match, losing all references.Resolution:
Fixed to always send id and flowxUuid for existing params when saving the operation, preserving variable references.
Updating parameters in the config page caused existing parameters to be replaced with new ones, generating new flowxUuids. This caused variables in database nodes to no longer match, losing all references.Resolution:
Fixed to always send id and flowxUuid for existing params when saving the operation, preserving variable references.
Build Export Timeout
Build Export Timeout
Problem:
When exporting builds with multiple resources, some resources remained in EXPORTING status, others got EXPORT_TIMEOUT without the build export receiving the status, and others had EXPORTED status. This was caused by Kafka messages being processed before the MongoDB transaction was committed.Resolution:
Fixed the export function to ensure proper sequencing of database transactions and Kafka messages during build export operations.
When exporting builds with multiple resources, some resources remained in EXPORTING status, others got EXPORT_TIMEOUT without the build export receiving the status, and others had EXPORTED status. This was caused by Kafka messages being processed before the MongoDB transaction was committed.Resolution:
Fixed the export function to ensure proper sequencing of database transactions and Kafka messages during build export operations.
Platform improvements
Platform improvements
- Infrastructure
- AI Platform
Connector Topic Pattern
Added dedicated KAFKA_CONNECTORS_TOPIC_PATTERN variable for connectors, allowing custom topic patterns without breaking other components like document-plugin, data-search, and cms-core

