What's New

News and Alerts

Incident Report: 2026-09-30 – Degraded Experience in the EMEA Region

October 7, 2026

Overview

On September 30, 2026, customers using the Smart Flows shared cloud in the EMEA region experienced delays and interruptions in flow execution and document generation. Other regions and private cloud environments were not affected.

Cause

A defect in Smart Flows allowed a single, unusually long template compilation to block shared processing resources. While these resources were blocked, other flows that required template compilation could not continue. The issue was triggered by a regular template compilation.

Timeline (UTC) – September 30, 2026

The service was intermittently degraded between approximately 08:11 and 17:31 UTC.

• 08:11 - Flow execution and document generation began to slow down or stop.

• 09:11 - The service was restarted and processing resumed.

• 13:06 - The issue recurred. The service was restarted after diagnostic data was collected.

• 16:21 - The issue recurred and the service was restarted.

• 17:31 - The processing that triggered the issue was isolated to prevent further impact on the shared cloud.

Resolution

A fix for this defect is included in Smart Flows 4.29.2, released on October 6, 2026. Deployment to the EMEA shared cloud is scheduled for October 13, 2026. We will update this notice when the deployment is complete.

We are also working on further improvements to reduce template compilation times.

We apologize for the disruption to your operations and thank you for your patience.

Empty Documents Dropdown After Upgrading to 4.29

September 30th, 2026

Known Issue

After upgrading to Smart Flows 4.29, the Documents dropdown in the connected business application can be empty or incomplete. This happens when the system tags of the connector are not synchronized with the Smart Flows project. The flows themselves are not affected.

Workaround

In the Smart Flows Project Console:

1. Оpen Control panel > Tags

2. Select System

3. Select Sync.
   The flows reappear in the dropdown.

Run the synchronization in each connected project. No changes to flow or user tags are needed.

Breaking Change in Experlogix Documents 1.0.0.preview28: Child Form Data Schema Update

February 26th, 2026

Summary

Starting with Experlogix Documents version 1.0.0.preview28, a breaking change has been introduced in the output data schema of form data sets that contain child forms.

This change affects how child form data is exposed in the generated data structure and may impact existing downstream mappings in Smart Flows templates, flows, and other integrations.

Customers upgrading to this version must review and update affected mappings to ensure continued correct behavior.

What changed?

In versions prior to 1.0.0.preview28, the output data schema of a form containing a child form included an extra <data> element at the root of the child form structure.

As of version 1.0.0.preview28, this <data> element has been removed.

The child form fields are now exposed directly under the child form node, without the intermediate <data> element.

Impact

This change impacts all references to child form fields that rely on the old schema structure.

You may be affected if you reference child form data in any of the following:

• Smart Flows templates (data mappings, expressions, conditions)

• Smart Flows flows (data mapping, conditional logic, metadata mappings)

• Integrations or custom logic that consume submitted form data

• Any downstream processing that assumes the presence of a <data> element

If mappings are not updated, affected fields may:

• Resolve to empty values

• Cause validation errors

• Break downstream logic

Required action

Update downstream mappings

To mitigate the impact of this change, all downstream mappings that reference child form fields must be updated.

Specifically:

• Remove the .data level from field references

• Update mappings to reference child form fields directly

Example mapping update

Apply this update consistently across:

• Templates

• Flow blocks

• Conditions

• Metadata mappings

• Any other location where child form data is referenced

Why this change was made

Removing the extra <data> wrapper simplifies the data schema, improves consistency with parent form structures, and reduces unnecessary nesting. This results in cleaner mappings and a more predictable data model going forward.

Version information

• Introduced in: Experlogix Documents 1.0.0.preview28

• Change type: Breaking change

• Affected area: Form data set output schema (child forms)

Recommendation

Immediately after the upgrade to 1.0.0.preview28, we recommend:

1. Identifying all templates, flows, and integrations that reference child form data

2. Updating mappings to reflect the new schema

3. Testing affected flows and document generation scenarios.