Flow Designer | Problem with Update Sets and Compiler Build

[Joseba Ulibarr1]

Hello,

We have a problem when moving an update set from Test to Production.

* Background:
We cloned our Productive instance (Rome Patch 4 Hot Fix 1) to our Development and Test instances which had a more recent version (Rome Patch 4 Hot Fix 1a).
As Test and Development were formally already upgraded, they were scheduled to upgrade to the Hot Fix 1b.

* Issue:
We created an update set that performed a few modifications on one of our Flows. This update set was moved to Test without any issues.
However, when moving the update set to Production, we received a preview problem with Description "Found a local update that is newer than this one".

There are differences on three fields:
- Compiler Build
LOCAL: glide-rome-06-23-2021__patch4-hotfix1a-12-17-2021_01-11-2022_1246.zip
REMOTE: glide-rome-06-23-2021__patch4-hotfix1b-01-19-2022_02-08-2022_1831.zip
- Label Cache
- Remote Trigger ID

* Attempts to fix the problem:
- We have upgraded our Test and Development instances to the 'Rome Patch 4 Hot Fix 1b' version.
- We have created a new Update Set, perform a simple modification on the Flow so it was added to the Update Set
- Attempt to move the Update Set to the Productive instance.

This, however, has not worked as we are receiving the same type of error message.

* Questions:
- Is there any risk if we accept or skip this remote update? Would that break our Flow?
- Is there a way of easily fixing this problem?

Thanks.
Regards,
Joseba Ulibarri

[Hitoshi Ozawa]

Probably best to contact Now Support on this issue because the issue is with the subscription instances and with patches.

[Joseba Ulibarr1]

Support answer was not very clear on the reasons of the issue:

"From my look at it it does not appear that issues will be caused by accepting it (unless you have custom configurations that are related to its remote trigger id). As a precautionary measure if you choose to accept, you can export the current version as XML and import it back in at a later date if you so choose, in addition to being able to revert the update."

I finally decided to create a new update set, clone the Flow that was generating the conflict, and promote it to my Productive environment. I then manually disabled the original flow.

[Shubham Arya1]

Did you disabled original flow or the duplicate one you took to the production environment