Forum Discussion
"Sorry, something went wrong" is killing me today!
I am experiencing a high frequency of 'Sorry, something went wrong' today 2/27/2018. It is preventing me from getting work done. It is mostly in settings for example:
From the Settings Page:
Site Collection Administration > Content type publishing - Bam! Sorry .....
Search > Schema - Bam! Sorry......
Site Collection Administration >Search Results Sources - Bam! Sorry...
and More!
1 Advisory in Service Health for SPO (SP129758) - But it is related to Project in specific scenarios.
I am used to refreshing the page and retrying occasionally, but this is different and extreme.
Anyone else having this problem today?
4 Replies
I've received these so many times myself. Today is very very bad (1st March 2018)
I am sure it's a congestion issues in MS Flow cloud. Even flows that are known to work show me this message when triggered. Also, simple HTTP request to list the flow names from SharePoint takes 30-40 seconds for fetching 3 elements.
I am also sure that there is nothing we can do about it. The quality of the service is low right now
- Is this happening on any kind of SPO site (Classic and modern)? I have just browsed a couple of sites in my test tenant and no issues so far
jcgonzalezmartin - Yes this is happening in classic site collections. I was actually going to work on this project now (2/28/18 - 3:41pm PST) ..... and Bam! When I select 'Content type publishing' under the Site Collection Administration settings I receive "Sorry, something went wrong
An error occurred during the compilation of the requested file, or one of its dependencies." I just selected 'Search Schema' and 'Search Results Sources' and the initial page loads, but on Search Schema, when I do anything else I get the "Sorry, ..... " message. I was hoping it was a passing problem, but it looks like I may have to open a Premier Ticket. Thanks for your reply. GregI have been having this problem for 2 days. I have screenshots and documentation and 40 Minutes after recording the links that generated the errors Premier Support called and I could not reproduce the problem. Well I hope it stays fixed because I have some work to do now.
