@Andrew I'd like to understand our options a bit and also tagging @Pginer-WMF and @Nikerabbit so you're aware and can chime in. The tool instance in question is one that's actually being used as the back-end for Content Translation recommendations. We have a replacement on LiftWing and are making progress towards deprecating this Cloud VPS instance but aren't there yet and I don't know the exact timeline. The task for the switch is T365347 and there's a bit more discussion at T308164#9809590.

I don't think it's a good idea to migrate for a few reasons:

• This is a legacy system that is unmaintained and I honestly am not sure if I could fully fix it if something broke in the transition to a newer VM.
• We should be close to just deprecating the recommendation API on tool and so I'd prefer not adding the overhead of migrating it (especially given the unclear nature of how to fix it if the migration is not smooth).

My questions:

• @Nikerabbit: can Language move all of the recommendation traffic off of the instance and to LiftWing by June 30th? In which case, we can just proceed with deprecation.
• If not, @Andrew what are our options for going beyond July 15th?

We're targeting a fix for T365347: Update endpoints used in Content and Section Translation to use the LiftWing version of the Recommendation API to be included in next week train.

We're targeting a fix for T365347: Update endpoints used in Content and Section Translation to use the LiftWing version of the Recommendation API to be included in next week train.

Great news @Nikerabbit -- I'll watch that task then but sounds like we should be good to deprecate by July 15th then assuming all goes smoothly. @Andrew I'll follow up with you if we end up needing an extension.

Sounds good! Thanks for keeping track of this.