Table 'sys_hub_trigger_instance_v2' does not exist

[ahmadfaiz]

Getting this above error when we are moving our flow from Dev to Prod, I tried with two different flow, and subflow but getting this same error, and not flow is moving to Prod, only name is available but inside it, there is no action, steps or anything

these are the error that I am getting,

There could be a reason that Dev is current Xanadu and Prod is current Vancouver. But we are not sure whether this is any issue or not

[Robbie · Accepted solution]

Hi @ahmadfaiz,

I was going to ask what the version differences are between Dev and Prod, however you've provided that information.

Out of interest - do you operate with a Test or SIT instance between Dev and Prod?

I believe (but I would confirm this) that the 'sys_hub_trigger_instance_v2' table is a new table introduced with Xanadu.

You clearly have some code which is referencing this table and thus causing an issue when pushing to Prod.

Whenever pushing to Prod, the code and update set (Release package) should be verified on an instance/environment that mirrors Prod. This is typically a Test or SIT instance.

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.


Thanks, Robbie

[ahmadfaiz]

Hi @Robbie,

Yeah, currently we are having upgrade process going on, As of now our Dev and Test instance both are in Xanadu but Prod is in Vancouver. So maybe this is something which is causing issue, as while moving update set from Dev to test, it didn't throw any error. But same update set when moving to prod caused this issue.

[Robbie]

Hi @ahmadfaiz,

I appreciate there's always an expectation from clients/stakeholders to deliver, but when upgrading environments, I always implement a change freeze for this very reason. Otherwise you're trying to manage and support moving targets.

As you've stated you have the standard 3 environments, I would absolutely ensure at least the 'Test' environment is frozen. This is required so as to have a mirror of Prod in case of any issues that occur with Prod (It should go without saying it is not recommended to fix bugs in Prod).

Dev can then be used to apply the upgrade to and run tests against the latest version.

This approach, like all upgrades requires planning and comms with stakeholders so everyone is aware.

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.


Thanks, Robbie

[Steve Gibson]

To aid with anyone else looking at this.

Error Table 'sys_hub_trigger_instance_v2' does not exist - Support and Troubleshooting (servicenow.c...

Details

When creating or updating flows in ServiceNow Instances beginning in the Washington DC release or later, the newly created flows will utilize Flow Engine V2. Previous releases of ServiceNow including Vancouver, Utah, and earlier do not utilize Flow Engine V2.

When importing a Flow that utilizes Flow Engine V2 into release where that engine is not available the following error will be seen:

Error Table 'sys_hub_trigger_instance_v2' does not exist

We do not support importing flows from newer versions of ServiceNow to older versions of ServiceNow. As Flow Designer is developed changes are made between releases, this can cause major issues for flows that are imported back to older versions of ServiceNow.

We recommend upgrading your instances to match versions so that flows can be transferred between them.

The world works with ServiceNow.