Literally every time ESRI pushes out an ArcGIS Online update does it cost us a day of work while they fix whatever issues the latest update has introduced. It's beyond a joke now and is incredibly hard to defend to colleagues and clients. The stress testing of these updates needs to be properly done before pushing it out instead of beta testing them on paying customers
Totally agree. It was a hassle for me to login in just to leave this comment. That's pretty embarrassing especially leading right in to the ESRI UC. We've switched our public facing parcel viewer site from an outside vendor to Experience Builder and when ESRI doesn't properly test their updates it leads to a stress filled day for our office being inundated with angry taxpayers.
Totally agree too.
Having issues this morning as well
Very slow today. No noticeable differences so far. Been trying to work since 7:30 EDT this morning.
Agree! Come on ESRI, losing money and wasting time right now. Its not just AGOL either, every Pro update breaks a whole bunch of things in my workflow, even when I wait a few patches. Its completely ridiculous.
Good I'm glad I'm not making it up that AGOL is very sluggish this morning.
The console logs seem to show its basically the sharing and oauth that is haviing issues trying to access tokens - probably due to the new user types added with this update.
Amen
I agree! I feel like they must be super disorganized behind the scenes because all their products are like this. They rely on their customers to test things and it's never gotten better. It does seem like somebody could have attempted to log in after this update though and they should have rolled it back.
The part I like less is how in the dark customers are with the status, ETA fix, ... this has a serious impact on severals things for us, .... it's been 4 hours at least.
I just reached out to Tech Support - our whole organization site is down and I can't log in to either our site or arcgis.com.
When our site does load, all the menus are gone......
100% agree. We're loosing confidence with our end users each time this happens, and all we're doing is responding to frustrated users.
If anyone from Esri is reading this, is there any potential for you to roll out the update to everyone as a separate login option and then give users the option to work on the old or the new version for a few weeks? Give time for issues to be worked out and then launch the update proper? I'm aware that we can sign up for the early adopter beta but this probably only attracts a few hardcore who have the capacity to provide feedback. It would be great to be able to test out the new functionality after an update but have the option to revert back if things go wrong in the same way you can maintain an old version in Survey123. I'm sure I'm oversimplifying this of course but additional options to avoid these kind of issues would be much appreciated. Thanks
Jumping in on here as we have been affected by this as well. Thinking about other options from an organizational standpoint. If wanting to stick with Esri, then Enterprise for everything internal and AGOL for anything public facing? So if then issues with AGOL updates it does not affect our internal day-to-day? Any one here have thoughts or ideas on the matter? (We've discussed open source possibilities but we are so ingrained with Esri products and apps as an organization it would be a massive undertaking to switch.)
It seems to happen every year like clockwork... it would nice to at least have a heads up what day the update is happening so we can plan around it and warn our customers that our services will be down.
Strongly agree. Our whole site is down. Field staff can't access field apps. Every time this happens it gets harder to convince leadership that we should stick with Esri.
@AdamGaudet this is exactly what we do. Having control over our update schedule is worth lagging behind the newest features a bit.
CTRL + Z, ESRI. We can't work.
...and this is all before we discover all the application breaking bugs (and occasional "intended behavior"). We'll then call technical support who will give us the runaround and have us spend days of work doing arbitrary troubleshooting steps having nothing to do with the issue at hand. We close more than half of our support cases out of frustration and/or when we find a workaround the hot buggy mess that has become the norm for most Esri products.Honestly, we're starting to move more and more workflows off the Esri framework and into our other enterprise applications wherever possible. As web applications become increasingly mission critical to our everyday operations, we need stability above all else. Esri tools are very powerful when they do work as intended and we'd love to continue using them. There was a time when I swore by Esri products. Please get it together and turn things back around, Esri.
I agree. We have staff who got up early and drove for hours to get to their project sites and now can't use Field Maps. None of our desktop users can sign into Pro. Client-facing web apps are down. I just had to send out an embarrassing email to my whole organization letting them know that Esri released a bad update and all I can do is monitor the situation and keep them posted.
I second @MichaelMorisette's request for stability above all else.
We can't do our jobs today. We'll be seriously reconsidering whether Esri provides the service reliability we need when building mission-critical applications. I fully understand that the people who work at Esri are human just like the rest of us, but the system they've built has to be more than that, and the updates they publish need to be human-proof. This cannot happen when some of Esri's services are relied on for life-or-death decision-making.
The early adopter community exists, but they didn't have any release notes or details on what changed. So there wasnt even really a proper beta this go-around.😤
Honest question to those who are expressing considering moving off of ESRI - what alternatives are you looking at? I totally get that a planned and scheduled update causing these issues is very poor (and this one in particular seems a doozey), but ESRI does usually get these fixed relatively quickly, and I'm unaware of any other software companies that never have any upgrade errors and problems.
Update: I just was finally able to sign into Pro. Maybe things are getting resolved.
On another note, I can't believe I haven't gotten an email from Esri this morning. ArcGIS Online Administrators should have been notified as soon as they realized there was a major issue. I shouldn't have to come on here to find out why nothing is working.
@ZachBodenner I agree, I think the software is generally fairly stable and has massively improved our service offering. I think we've just had a few issues after updates in recent times (particularly in the UK where our preferred projection British National Grid has been missed out of updates on 3 separate occasions!) and I think that colours people's perceptions. I was quite looking forward to checking out all the new functionality this morning and have spent the day dealing with issues instead. It would just be great if there was a way to revert the old version or test the new version for longer to resolve some of the issues before launch.
I always expect a certain amount of hiccups when software updates are deployed, so that doesn't really bother me that much - as long as it's resolved asap. When it doesn't get resolved or I have very little communication on the status of something, that's usually when I get frustrated.
From my experience, I can 100% say I would rather use ESRI products any day. It's a lot more robust than other software, a lot easier to train on, doesn't require coding (because it's shouldn't require a background in programming to do GIS), and the documentation available is better than other platforms. So I wouldn't want to switch to something else because it would give me a whole other host of problems. In addition to the fact that my users would not be getting an accurate reflection of what the industry is (if they don't know how to use ArcGIS)
Long story short - issues are going to happen, and that doesn't automatically mean the software is bad. Technology is always going to have problems because that's the nature of the business. It only matters how we communicate it and how we work around it.
#digitaliteracy4life
We're on day two now and much of our org's online content will still not load in either ArcPro or AGOL. This is genuinely baffling and the lack of clear messaging from ESRI makes it difficult to explain to the rest of my org why this is happening and when it'll be fixed.
@OllyD seconded. Feature services are all inaccessible or showing as corrupt.
"No 'Access-Control-Allow-Origin' header is present on the requested resource."
@SaraJL Fully agree. They are a monopoly for a reason - nothing else comes close at an overall platform level.This has unfortunately led to us being treated in a way that would not happen if there was decent competition in the market. I, for one, am sick of being gaslit all the time that it is my hardware, my software, my data, my network, my whatever, every time I report an issue to a mandatory local reseller or in this Community. Complicated software has issues -100%.Good companies mitigate this in various ways - dropping feature + fix heavy versions every six months is not one I feel is the best.I'm typing this on a Saturday morning while waiting for an Offline Area to package in FieldMaps for people going bush Monday. I don't know if the failures are me or AGOL and there is nothing in the Community except Esri staff telling people to report issues to the local resellers, that don't work on weekends if you're not a big government client...
Connectez-vous pour publier, suivre du contenu, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
