Unable to capture Flow Designer flows in update set -- facing issue with flow version reference
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
I have my source instance where I had setup all my custom flows, custom subflows, custom actions and some custom tables and fields. However, I had recorded all of those in the Default Global update set. Later, I moved all the records in the default update set after 10 Oct 2025 to a newly created update set, exported the new update set and imported it into the target instance. However, I get a lot of errors after I preview the update. All of them have the same error message: "Could not find a record in sys_hub_flow_version for column version_record referenced in this update "
Why weren't the version records captured in the update set? What can I do about it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12 hours ago
navigate to [sys_update_xml] table and in the payload field you can search for the sys ID if you know it... if not, perhaps you might search for it according the type, created on, created by or other attributes...
If it is not found, it might have been overwritten by a newer version or deleted. For that, navigate to the Deleted records
/* If my response wasn’t a total disaster ↙️ ⭐ drop a Kudos or Accept as Solution ✅ ↘️ Cheers! */
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12 hours ago
Sorry, the sys ID of what should I be searching? And why would there be any potential overwriting by new instance if I have custom flows and tables?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago
Which sys ids should I be searching? Also, why would any data get overwritten in the new instance around flow versions if all my flows are custom with custom actions? Can you provide some sort of step by step?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12 hours ago
rather than moving customer updates from default to your new update set
re-capture the flow, subflow, actions again in your update set and then migrate that.
💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
