Pages are randomly showing a blank screen since the last update. Need to refresh to load page.

I have the exactly same issue. It seems to be related to service-wrokers, to be precise with service worker auto preload and happens only in MS Edge.
The issue occurs, when the service worker is installed but not yet running. When accessing the web app for the first time the service worker is started automatically but cause of service worker auto preload the mainpage is fetched before it is fully started. This results in the blank page but I don't know if its a wrong implementation of service worker or a bug in MS Edge. However the issue occurs only since version 143 and only in MS Edge so if it's not a bug it is at least a breaking change.
The related issue in the vaadin repo:
https://github.com/vaadin/flow/issues/22954

I have exactly the same issue, and it broke my Power Automate instance. I tried resetting Edge, updating it, and even reinstalling it, but none of these solutions have fixed the issue so far. Unfortunately, no solution has worked for me, and my Power Automate setup is no longer functioning.

The documentation of the auo-preload feature that seems to be causing the issue here says:

When the fetch handler responds without calling fetch(e.request), the auto preload network request is simply discarded. When the request is modified with Request.clone(), or the new request is created inside the fetch handler, a new network request is dispatched and the auto preload network request will be discarded, too.

So I tried to simply clone the request before passing it to the fetch method and that seems to work.
In my case the service-worker is using the workbox libary with work-box routing and NetworkOnly strategy. In this case you have to create a copy of the RouteHandlerCallbackOptions which gets a clone of the request, and pass it to the strategy:

const newCallbackOptions = { request: orgCallbackOptions.request.clone(), ...orgCallbackOptions };
return await networkOnly.handle(newCallbackOptions);

This way the (buggy) auto-preoad should be discarded.
In my case I only apply the workaround when running in MS Edge > 143 to make sure other browsers are not affected by potential negative side effects.