Flow Designer Issue- Xanadu Release

[nikitanegi255]

in XANADU-One of the main issues is the introduction of new Flow Designer tables, which is preventing update sets touching these new tables from being promoted to the current QA and UAT instances. Though my DEV instance is in Xanadu, and knowing it has the issue, so I don't want to promote my update sets to QA and UAT.

any resolution/workaround is requested.

[Abhishek_Thakur]

Hello @nikitanegi255 ,

Recently I also landed up into the situation where we had an upgrade. So, in your scenario, it won't create any performance issue in your instance if you push this for QA as this is expected OOTB behavior.

Please mark my answer as accepted solution and give thumbs up, it it helps you.

[Abhishek_Thakur · Accepted solution]

Hello @nikitanegi255 ,

If you found my response helpful, could you please accept my answer. So, it will also help others if they will get into the same scenario.

Thanks,

Abhishek Thakur

[terrieb]

Where is the Solution for this?  Everytime I click on the "View solution in original post" it just comes back to this page.

Thank you

[Community Alums]

It is not about the performance issue but the Flow execution is failing. When the update sets are moved from higher version instance to lower instance version ,it is not executing appropriately. There are lot of fixes that has been done in the flows, may be that is causing the issues: https://www.servicenow.com/docs/bundle/xanadu-release-notes/page/release-notes/quality/xanadu-all-ot...

Please mark this as helpful if this helps.