@Joseph_Devlin Here is their response.
They have emailed me the issue.
This is what they said:
On checking internally, we got to know that your translator has failed for 1.5 years and you have not had a client connect in some time, that is why the feature flag to continue showing the sync page did not get added to this application.
Your app should be restored to its normal state now. Please let me know if you have any further concerns, I will be happy to help you.
MongoDB Team
The device sync app hasn’t been working for 1.5 years. This could be true! Just a quick overview of my application when logging into your account you had to pull through default information to your organisation and then sync that default data with the organisation data. this only happens in a new organisation. around 1 year ago we implemented a different method to create these new organisations by automatically populating the organisation’s data with the default data so this method could be removed. The code however still triggered the DownloadAndSync() function.
I am still confused as to why my application was still able to work until the deprecation notice was announced and then only for it to fail if it has failed for 1.5 years.
I do acknowledge that we should have removed the DeviceAndSync() function once we implemented the new method, however, if the translator had failed surely my application would have stopped working 1.5 years ago which would have allowed us to find out sooner.
Another thing I’m slightly disappointed in Mongo for is the lack of alerts regarding this. surely there should be some error notifications that can alert me or anyone else if the “translator” fails. This will allow teams to get onto the issue immediately and not have to wait 1.5 years for their application to stop working and then spend hours sending emails back and forth for a whole week to determine that was the issue.