I can see it ok from my end, when it fails could you grab the JS console logs from your browser and send them? Thanks

[Info] (main-BXaHVRWD.js, line 103)

_____

___ |[]|_n__n_I_c

||||###|___}

O-O--O-O+++--O-O

•                                  *

•       Enjoying Railway?          *

•                                  *

•     Want to ride with us?        *

•                                  *

•          Hop aboard,             *

• the train is leaving the station! *

•                                  *

•  https://railway.com/careers     *

•                                  *

[Error] Error: Minified React error #418; visit https://reactjs.org/docs/error-decoder.html?invariant=418 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

reportError (react-dom-CWIgXKDx.js:6:4764)

Ll (react-dom-CWIgXKDx.js:8:40604)

Il (react-dom-CWIgXKDx.js:8:39772)

vl (react-dom-CWIgXKDx.js:8:35014)

te (react-dom-CWIgXKDx.js:1:1618)

se (react-dom-CWIgXKDx.js:1:1988)

[Error] Error: Minified React error #423; visit https://reactjs.org/docs/error-decoder.html?invariant=423 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

reportError (react-dom-CWIgXKDx.js:8:44712)

Ll (react-dom-CWIgXKDx.js:8:40604)

Il (react-dom-CWIgXKDx.js:8:39772)

vl (react-dom-CWIgXKDx.js:8:35014)

te (react-dom-CWIgXKDx.js:1:1618)

se (react-dom-CWIgXKDx.js:1:1988)

[Info] Successfully preconnected to https://fonts.gstatic.com/

[Warning] Source Map "https://cmp.osano.com/qVHEV4lSSU/738deb1e-f024-459e-ae0a-2e6a0d461ea8/osano.js.map" has invalid "mappings"

[Warning] Source Map "https://cmp.osano.com/qVHEV4lSSU/738deb1e-f024-459e-ae0a-2e6a0d461ea8/osano-ui.js.map" has invalid "mappings"

[Info] Successfully preconnected to https://fonts.googleapis.com/ (x2)

[Warning] The resource https://fonts.gstatic.com/s/ibmplexserif/v20/jizAREVNn1dOx-zrZ2X3pZvkTi3s-CI0q1s.woff2 was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it wasn't preloaded for nothing.

[Info] Successfully preconnected to https://merchant-ui-api.stripe.com/

[Error] Blocked a frame with origin "https://railway.com" from accessing a frame with origin "https://js.stripe.com". Protocols, domains, and ports must match.

ht (posthog-recorder.js:1:17033)

ht (posthog-recorder.js:1:19982)

ht (posthog-recorder.js:1:19982)

ht (posthog-recorder.js:1:19982)

we (posthog-recorder.js:1:82084)

st (posthog-recorder.js:1:85009)

Oe (posthog-recorder.js:1:85106)

Sh (posthog-recorder.js:1:154187)

start (posthog-recorder.js:1:143794)

hr (modal-CoBSJFZ6.js:4:56961)

(anonymous function) (modal-CoBSJFZ6.js:4:55275)

(anonymous function) (modal-CoBSJFZ6.js:2:5317)

[Info] Successfully preconnected to https://api.stripe.com/

[Warning] [canvas] sync slow – {projectId: "0f12b18e-24a9-49f1-8327-ad2633ac1452", environmentId: "628cc6d9-aab6-42f2-8793-95ddbb2dc792", syncStatus: "slow"} (posthog-recorder.js, line 1)

Thanks for grabbing those! The two errors that matter are both hydration failures:

• React #418 — the server-rendered HTML didn't match what the browser tried to render.
• React #423 — React then tried to recover by re-rendering the whole page on the client.

When that recovery also stalls (which lines up with the [canvas] sync slow warning and your note about the connection), the project view never finishes painting — which is why clicking into a project shows nothing. The Stripe cross-origin and Osano source-map lines are just normal warnings, not the cause.

This usually happens when a stale cached version of the page gets loaded against a newer build of the dashboard. A couple of things to try:

1. Hard reload to clear the cached page: Cmd-Shift-R (Mac) or Ctrl-Shift-R (Windows/Linux). If that doesn't do it, try the dashboard in an incognito/private window.
2. If you're able to, try a different network — the sync slow signal suggests the connection is dropping part of the page load.

Let us know if it still won't load after a hard refresh and we'll dig in further.