Migrate a new topic to test instance but getting error: This topic version is not supported on...

[Gil6]

I sent a promotion to test of a new topic for the VA. The engineer in charge promoted it but now when I tried to open the topic, I receive this error: This topic version is not supported on this instance. Check with your ServiceNow Administrator for assistance.

*Note; I'm new with virtual agent. I know that the test instance is on Washington version and dev is Utah.

how can I fix that? 

thanks,  

[Mark Roethof]

If you want to deploy it to all your instance, which I do assume, then yes, all the instances need to be on the same release. Thats not for all ServiceNow development, though it is the case with VA topics.

[Sandeep Rajput]

Incompatibility issues can arise from Flows too..

[Mark Roethof]

In theory its also just a bad practice, though for most in ServiceNow it will go fine. Some areas, like VA are just really technically blocked like this topic is perfectly showing.

Anyway just better to avoid transferring development between different versions.

[Gil6]

Thanks a lot both. 

Now, this weekend they are going to clone test instance  which is on Washington to the partnerDev env.
this topic in question, was develop in the current version in the partnerDev which is Utah.  
they sent a communication that we need to save our work from the partner dev in an update set (which I already did). 

If after they migrate the partner dev instance to Washington, could I have issues importing this code from the backed up update set ? due it was develop in another version.

[Sandeep Rajput]

@Gil6 You can expect to have the similar issue, since the update set was developed in Utah which contains the VA feature which is compatible with Utah release but not with Washington release. Hence the same issue will crop up while importing the update set.