
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2025 08:21 PM
Hello.
I know that flow engine is upgraded from V1 to V2 in Xanadu.
Due to this, my scoped app developed in Xanadu dev. instance can't be installed into Washingtondc instance.
Of course installation result shows as 'success' and there is no error message found.
But flow is not updated actually after installation.
I've found knowledge article below, but it says 'We do not support importing flows from newer versions of ServiceNow to older versions of ServiceNow. We recommend upgrading your instances to match versions so that flows can be transferred between them."
(https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1700893)
So my question is, is there any alternatives for changing default flow engine to V1 for each flows?
or does SNOW have any plan to support auto migration to V1 when app is installed into Washingtondc?
Anyway, I think this is too restricted limitation because if it is common scoped app for big company,
it needs to be deployed to various instances.
So we are developing scoped app with consideration of lower version compatibility by ourselves and also doing regression testing.
But I've never seen this kind of BIG restriction when SNOW is upgraded.
It will be very big challenge for us to prepare every version of dev. instances for common scoped app.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2025 08:54 PM
I think you will have to follow that KB article only.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2025 08:54 PM
I think you will have to follow that KB article only.
If my response helped please mark it correct and close the thread so that it benefits future readers.
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-30-2025 04:27 PM
Thanks. You're right.
Finally, I've confirmed with SNOW that there is no way to deploy flow from Xanadu to Washingtondc.
XML format for flow from Xanadu is different with Wanshingtondc. It uses new tables that has '_V2' suffix that does not exist in Washingtondc.
PS. For someone searching answer like me, there is a KB that enables flow runs on V1 engine with some configuration, but it is not related with deployment. It is only for run for certain instance.