Skip to contentSkip to navigationSkip to topbar
On this page

Upgrade notification for v1.33 customers


Following the release of Flex UI version 1.33, we have had reports from some customers of unexpected breaking changes when upgrading to v1.33 from a previous version. If you were affected by this, we are very sorry for the impact this may have caused. We intended these changes to be backward compatible to avoid introducing breaking changes in minor versions. After investigation, the changes are too large to overcome with further updates.

To resolve the situation, we have decided to revert the changes that were introduced in v1.33 in the upcoming v1.34 release. This will restore the original behavior that was present in v1.32 and lower but it means you will need to revert any changes you made to accommodate the changes in v1.33. Please read the following guidance to understand how this might affect your account:


If you made no changes when upgrading to v1.33

if-you-made-no-changes-when-upgrading-to-v133 page anchor

You should not need to make any further changes and can upgrade to v1.34 as soon as it's available. We always recommend testing a new version before production usage. We also encourage you to start planning your migration to Flex UI 2.0.


If you uncovered issues with v1.33 and reverted to a previous version (v1.32 or lower)

if-you-uncovered-issues-with-v133-and-reverted-to-a-previous-version-v132-or-lower page anchor

You can skip v1.33 and upgrade to v1.34 when it is available. We always recommend testing a new version before production usage. We also encourage you to start planning your migration to Flex UI 2.0.


If you uncovered issues with v1.33 and made code changes to address them

if-you-uncovered-issues-with-v133-and-made-code-changes-to-address-them page anchor

You will need to revert the changes back to the previous state that was working on v1.32 (or lower) before you upgrade to v1.34. Alternatively, you can plan to upgrade to UI 2.0 as all GA versions of this major release include the Sync removal changes.

We apologize for the inconvenience this version release has caused. Please contact your TAM or our support team if you have additional questions.


What changes were made?

what-changes-were-made page anchor

The changes were caused by changes we made to remove Sync as a dependency from Outbound call, Conference management, and Internal transfer workflows in the Flex UI. The situation was further complicated by the upcoming End-of-Life deadline. To learn more about the changes, see the note posted on the Release notes.

Why are the changes being removed from v1.33?

why-are-the-changes-being-removed-from-v133 page anchor

Customers reported issues and some had to make changes to accommodate, which breaks our "no breaking changes" policy in a minor version release. We are restoring the previous behavior so there is a stable version of Flex UI 1.0.

What is happening on Flex UI 2.0?

what-is-happening-on-flex-ui-20 page anchor

Sync removal changes are still in place and will remain. It will be covered as part of the migration to this new major version.