This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Howdy y'all,
We currently have a shared list setup which has multiple users, however one of our users regularly gets this error when opening the list - Something went wrong: Invalid argument: 'header's missing application ID header. He states he simply opens the list and the error populates, refreshing a few times fixes it.
For some reason I can't attach a image. But all it states is the error above with a spilt ice cream cone.
Thank you for any assistance.
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Our tenant now has an open ticket where I referenced incident SP664797.
It has been, and I quote, “expedited,” with an ETA for a fix being August 9.
Hi All,
Currently, there is an ongoing incident posted to the Service Health Dashboard (SHD) as incident SP664797.
Title: Users are intermittently unable to access lists in SharePoint Online
User impact: Users are intermittently unable to access lists in SharePoint Online.
More info: Affected users receive the following error when attempting to access lists: "Something went wrong: Invalid argument: 'headers' missing application ID header"
Current status: Our investigation has determined a recent feature update introduced a request-handling issue resulting in intermittent impact. We've developed and initialized the deployment of a fix to address this issue and anticipate this will complete, remediating the impact, by Wednesday, August 9, 2023. We're continuing to monitor the deployment as it rolls out and expect some users may see remediation as soon as our next scheduled communications update as the fix progressively saturates throughout the environment.
Scope of impact: Your organization is affected by this event, and any user attempting to access lists in SharePoint Online is impacted.
Start time: Monday, July 24, 2023, at 7:00 AM UTC
Root cause: A recent feature update introduced a request-handling issue resulting in intermittent impact.
Next update by: Friday, August 4, 2023, at 7:00 PM UTC
Your understanding is highly appreciated.
Sincerely,
Jazlyn | Microsoft Community Moderator
I checked just now (6:28PM UTC) and this incident is not appearing on the Service health dashboard even with SharePoint Online checked. When can we expect it to show up?
Wow, 15 different broken flows today, business is an absolute mess and no response from our ticket with microsoft and absolutely no acknowledgement from anyone from microsoft in the forms. This is just incredibly unprofessional.
Well you currently have at least 65 people on this article telling you it's a problem. Maybe escalate and acknowledge that it's a problem instead?
Fantastic, we're having this issue too which means I'll need to put in a support ticket and get connected to a Tier 1 rep who is going to ask me "is your computer on" level-questions and have me run a ton of logging for something probably 1,000 other customers have already reported, despite having nothing to do with my local system. I hate it here