Table 'sys_hub_trigger_instance_v2' does not exist

ahmadfaiz · ‎09-25-2024

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 · ‎09-25-2024

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

View solution in original post

Kim Sullivan · ‎10-16-2024

This is a frustrating response from SN Support. I don't know any developer that doesn't go through some upgrade gaps between DEV and PROD. And not being able to move Flow changes during that gap is unacceptable.