SharePoint Online Webparts Not Loading Correctly Until Page Refresh

[Matthew2370]

I have multiple SharePoint Online site collections that are all exhibiting the same problem with certain webparts. When a page loads that contains a quicklinks, hero app, or weather app, the wep part will randomly not load correctly. When it fails, the web part will format incorrectly, will be missing content (document or webpage links), or will be placed on the page incorrectly.

For example, I have a page section with 3 columns, each containing a quicklinks webpart with links to documents. 50% of the time when i load that page, the first column does not show at all, the second column has the quicklinks header but no content, and the third column has the quicklinks header and content icons that have been shrunk with no link descriptions. I refresh the page, and the intended formatting loads correctly, showing all webparts and content.

I have multiple pages that this occurs to, with different combinations of webparts and content. Has anybody seen this before?

I have an attached example of a 2 column wide page section. The first image is initial page load, and the second image is after a manual refresh. (This issue happens in Chrome, Edge, Firefox, and IE)

[#2]

We have been having reports of the same issues on our modern SharePoint sites. Seems to have started happening more over the last couple months

[#3]

Agreed @Rick DeFoe.  I created a SPFX WebPart that queries the search service, and surface the web part on a page that I use with managed navigation (thus the search is context specific to the navigation link selected in the menus).  The webpart is not refreshing on the transitions.  Oddly if you select the same managed navigation menu link twice, it refreshes...otherwise a manual refresh is needed.  I'm exploring ways to try to force a refresh/reload of the page via HTML/Javascript and suspect I'll need to tweak the master page. 

[#4]

I am experiencing the same, have you resolved this? @Matthew2370 

[#5]

Hey @Scrum5,

I ultimately had to get into the Type/Javascript level on this to get it to work (window, etc).  Managed to nail it down by adding this to my Init code in the SPFX web-part.  Hope it helps you!  

*****

  protected async onInit(): Promise<void> {

    await super.onInit();

    navterm = window.location.pathname.substring(window.location.pathname.lastIndexOf('/') + 1);

    ((history) => {
      var pushState = history.pushState;
      history.pushState = (state, key, path) => {
          pushState.apply(history, [state, key, path]);
          this._onUrlChange();
      };
    })(window.history);

    window.addEventListener('popstate', function (e) {
      // Currently browsing by the browser history buttons ( back / forward )
      // doesn't cause any effect on a sp conditionally loaded page.
      // this._onUrlChange();
    });

[#6]

Hi, I am experiencing the same problem: certain web parts are not loading, manual refresh is necessary. This is not acceptable.
Is there a solution in sight? I should not be forced to add javascript, this should work out of the box.

[#7]

Hi, i've observed similar problem. My small investigation showed, that case depends on page layout.

Site collection welcome page is HomePage layout
First Load - all webparts are loaded correctly
to scenarios:
1. Navigate to page with layout ArticlePage (click link) - then return back with browser navigation button, some webparts on the bottom page are not loaded.
(need full refresh)
2 . Navigate to page with layout HomePage (click link)- then return back with browser navigation button, all webparts on the page are loaded.

This behavior occurs on one of several tenats i checked.
The same SPFx webpars, the same sections etc.

I think this is some kind of a native code bug rendering SPFx components

[#8]

Was this ever resolved as I am experiencing the same issue recently.

[#9]

Hey Andy...can't confirm I'm afraid I implemented the noted workaround in code and it worked well enough to move on (haven't circled back to see if the core issue remains).

[#10]

@Andy_Jackson nope, still an issue... And no comment form the Microsoft team :\

[#11]

We reported this issue at the start of April as well. It is important to note that it is impacting all types of SharePoint online sites (communications and teams). We have received reports from multiple users that content is missing until refresh. Thank you for continued work on resolving this important issue as many important links are being overlooked. 

[#12]

we are also facing same issue from last 2 months.