- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
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?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
I faced the same issue. As a Workaround I force the expected records from sys_hub_flow_version into my Update Set. As a final fix, in my understanding, this table should be captured automatically via Update Set (Adding the update_sync Attribute in Dictionary application).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Monday
This does not work. If I create my custom flows, subflows and custom actions completely from scratch, even then it throws the same error for not being able to find the version record in the new instance, even though it should have been captured by the update set.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Saturday
Moved all the updates to new update set is not the best option here, you have to capture all flows, subflows and actions again in new update set. Just make any minor changes in flows, subflows and actions, then save it.
I hope it helps!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Saturday
I did it earlier in a new update set, exported it and imported in a new instance. It gave the same reference errors
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thursday
Then check in detail the column version record mentioned in the error.
Is flow already present in target instance and you are sending updates?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Tuesday
We have the same error. What we did is check the sys_id related error in update set and export then import it to the target instance. After which we run the preview again and the error is gone. But I think this is only a workaround and should not be the case in the future.
