I am not able commit my update set to UAT instance

[Srinivasu2]

Hi Community,

I have updated my changes in dev and trying to move it to UAT

I have successfully previewed update set but while committing i got below error

"Update has been successfully committed but changes are not updated, please check update set log

than i checked update set log it is showing one of the log record is stating as below

Table "sys_hub_trigger_instance_V2 does  not exist"

Could you please help me how to resolve this?

Thanks & Regards,

Srinivasu

[GlideFather]

Create a new update set, make some simple change to capture it and try to commit it to see whether the error message is displayed always or just once... it will help you to realise if it is platform-wide or just a single update set.

After you know more, here are some tips:
- check the scopes,

- compare the environments version (it should match),

- Try to import/export via XML,

- Verify there is no naming conflict (two update sets with the same name),

- Verify that your update set in DEV has not been reopened (completed - then moved to in progress and then completed again),

- Delete the previewed records in UAT, and preview it once again,
- Check the [sys_mutex] table, filter the records for "update-mutex", if found, then delete the record from the "sys_mutex" table and try to preview and commit once again (be careful with this)

[Amit Verma]

Hi @Srinivasu2 

I suspect that you probably have a version mismatch between Dev and UAT instance. Can you please confirm the version of both the instances ?

Refer below screenshot -

Thanks and Regards

Amit Verma

[Srinivasu2]

Hi @Amit Verma ,

Can't we move my update set from dev to test instance if version are different

I see dev version is xanodu and uat version is vancover 

Please help me on this?

Thanks & Regards,

Srinivasu

[Dr Atul G- LNG]

Hi @Srinivasu2  you need to upgrade your UAT to Xanadu.