Honestly, I don't understand why everyone just can't wait a moment or two to wait for the fix. Obviously, they are trying to fix the situation, and I heard the developer found the issue and is pushing to prod soon (or something along those lines.)
Rolling back wouldn't be a smart thing to do. If it was triggered by a action it would occur again, maybe not the day of the roll back but in a few weeks. It would be just smart to fix the issue then push to prod.That state can be there for a few minutes, but not longer. If you notice that as an admin, you would roll back instantly.
You would roll back instantly. Getting the working state again is always prio 1. Obviously you would get a copy of the broken state to inspect in your dev environment.Rolling back wouldn't be a smart thing to do. If it was triggered by a action it would occur again, maybe not the day of the roll back but in a few weeks. It would be just smart to fix the issue then push to prod.
The real problem is that they didn't even have an announcement stating the issue and tell us the rough time to fix this. We can wait, but their attitude is so bad.Honestly, I don't understand why everyone just can't wait a moment or two to wait for the fix. Obviously, they are trying to fix the situation, and I heard the developer found the issue and is pushing to prod soon (or something along those lines.)
Make an announcement bruhHello everyone I just wanted to give an update,
We did push out a patch last night that worked for some time but things unfortunately crashed again. Our developers are working on it right now. I am so sorry for all of the issues!
Welp that sucks facepalmI dont have the power to![]()
when is this fixed?The error page (aka waiting page) will appear any time a download is not made available within a few seconds.
Previously, users would only be directed to this page for very large resources which took a few additional seconds to prepare.
After we changed our infrastructure and offloaded our attachment data, the additional delay of needing to transfer the resource to the main server where the injector software is located, was added to the overall processing time, and so the delay will occur for most resources now. Another change of infrastructure will be required in order to have the injector software run on the same server as the original attachment data.
That said, the problem you’re reporting and others are complaining about isn’t actually the waiting page, but the fact that if you get the waiting page, you will never get the download.
We’re in the process of updating our injector software, and we’ve run into some bumps.
EDIT (NOV 20): Development of new version of the software has been completed. Undergoing testing now.
