Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

What is the difference between "sys_hub_action_instance" and "sys_hub_action_instance_v2"?

bonsai
Mega Sage

After migrating flows using update sets, I visually check to make sure each flow action is updated correctly.

This is so inefficient that I'm looking into whether I can use table information instead.

Recently, I discovered that flow actions are stored in the "sys_hub_action_instance_v2" table.

It appears that flows migrated from the development instance using update sets are also recorded there.

In addition, the value field of the "sys_hub_action_instance_v2" record has a manipulated value set, so that the value between the development instance and the migration destination instance is the same.

However, the values ​​for some flows were not the same.

What's more, there were also flows that were not recorded in "sys_hub_action_instance_v2."

When I looked, I found that they were also recorded in "sys_hub_action_instance."

What is the difference between these tables?

I'm also curious about the instances where the values ​​are different.

 

I would like to share different values, but this is not possible because it is a corporate account.

1 REPLY 1

Ankur Bawiskar
Tera Patron
Tera Patron

@bonsai 

main difference between those tables is the version of the flow engine being used and the ServiceNow release.

sys_hub_action_instance: This table stores action instances for flows created using the original Flow Engine (prior to Washington DC release). It is used for flows and actions in older versions of ServiceNow and for flows that have not been migrated to the new engine

sys_hub_action_instance_v2: This table is introduced with the Flow Engine V2, starting from the Washington DC release. It stores action instances for flows created or migrated using the new engine. If you are on a newer release (Washington DC or later), flows and their actions will be stored here

Best practices

-> ensure source and target instance are on same release or target instance supports the flow engine used in source

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader