Known issues with adding a Flow to an Update Set?

[Jordan Blake]

Using an Update Set I attempted to move a flow I created to another Sub-Prod, but after committing the flow (without errors) the flow gave me an error when I attempted to load it stating that it cannot locate a record in the sys_hub_action_type_definition table. I had to manually find the record, and add it to the update set for it to work.

I understand that since the NewYork release the customer update for flows was flattened to one file (love that), but I fear this may be a bug. Has anyone experienced this or have any advice on how to better capture Flows under development?

[Miguel Donayre]

Quick question was the record in the sys_hub_action_type_definition, did that action come from  a spoke added to the platform? for example, the ADO or AWS spoke that was added and not part of the baseline? 

Or was the action in question created in house? 

[Jordan Blake]

It was a custom action we created.

[siva_]

sys_hub_flow is the table which is something related to flow 

 sys_hub_action_type_definition is something which gets generated when you create a custom action , 

it looks like you have not published the action in your exact update set and thats the reason , when you use the same in the flow , in subprod, it might not have found a link to the same. 

Action Definition ( sys_hub_action_type_definition ) might be the culprit here 

Regards , 

Siva.

[siva_]

I have an addional question regarding that custom action which i have asked here a couple of days back, just waiting for the response on the same. If you have any idea please respond on the thread here. 

https://community.servicenow.com/community?id=community_question&sys_id=1d620059db46d05011762183ca96...

Regards, 

Siva