MortenGuldbaek

Just adding a bit more context. This is almost exclusively happing when SPFx is loaded with the **listview-host-assembly** (link below), so only in Document Libraries / Lists. https://res-1.cdn.office.net/files/sp-client/listview-host-assembly_da-dk_b8ebd7d067e21a05dc5b8f78431fb6cf.js

This is still occurring on a regular basis for several of our clients. Is there any guidance or clarification on how to avoid this?

@nick-pape commenting since this was marked by you for Need:Attension. Are you able to tell if this is planned for a response, or in your backlog? Several of our clients...

We're keen to find a resolution as it's affecting our clients daily usage. Any updates or advice on how we might proceed would be greatly appreciated.

We were experiencing the same at 15.30 EST, but now it seems to work.

In my testing setup using localStorage, @azure/[email protected] seems to have fixed the superflous token request.

@ingin97 ok, that seems different to what we are experiencing. We are not using that flag.

Is https://cdn.{my-domain}.net/webparts/prd/2025.11.25.64207 your actual script name? I ran into issues where a missing appended forward slash was required

Our findings show that we are having to suffix the **cdnBasePath** (in /config/write-manifests.json) with a trailing slash to ensure it is not handled as a single script, but rather a...

@jansenbe certainly, here you go: Note: CDN is hosted on Azure, not SharePoint. Host, sub-domain, and path have been anonymized. **Trusted script sources record** https://mycdnonazure.contoso.com/assets/99999/ **Actual extension script (one of...