VCS root checksout old revision for changed URL

Hi,

we currently have problem with a changed URL of a SVN VCS root after an upgrade of Teamcity, first some background:

• We used Teamcity 2018.2
• We created a VCS root which pointed to http://<repo>/trunk/<project>/folderA and the last revision on that is 181785
• We created a build config which used this VCS Root via server side checkout with a checkout rule of: +. => checkoutFolder
• We created a branch from the old path under http://<repo>/branches/<project>/1.0.0/folderA and the revision of that is 182563
• The existing build configuration seemed to work just fine with this
• We upgraded to Teamcity 2020.2
• The existing build configuration did no longer work because it was saying:

  Failed to build patch for build <build info>, VCS root: <our VCS root>, due to error: Unknown path kind: none for http://<repo>/branches/<project>/1.0.0/folderA@RR[none => 181785_181785]@<some uuid>

As you can see Teamcity tries to checkout the old revision using the new path which does not work even on command line svn since for that revision the path does not yet exist.

We tried several things but all of them were in vain:

• Detach and reattach the VCS root to the build configuration 
• Deleting and recreating the VCS root which worked in the past for other users apparently:

  https://teamcity-support.jetbrains.com/hc/en-us/community/posts/206876175-Renaming-subversion-folders

In the end the only way we could get the build running again was to switch back to the old path of http://<repo>/trunk/<project>/folderA

So what could be the problem here, why does Teamcity try to checkout the new path using the old revision eventhough we deleted and recreated the VCS Root under a different name/id ?

P.S. our build settings are versioned in VCS and this was done back in Teamcity 2018.2