App on Community Cloud hangs on load: one static JS file never returns

Community Cloud
,
1

My app at https://supplier-resolver.streamlit.app hangs on most page loads. The repo is public: GitHub - martinstrell-source/supplier-resolver: Supplier entity-resolution prototype: confidence-tiered matching with a human review queue · GitHub

It’s currently running Streamlit 1.64.0 on Python 3.12.

What happens: The page shows the loading spinner, or it renders part way and leaves gray placeholders. In the browser’s network tab, one file under /~/+/static/js/ stays pending and never returns, while everything else returns 200. The stuck file changes from load to load. One time it was Slider.aBCDZLFJ.js, and another time it was useCollection.DOwgVAYY.js. The app logs show no errors, and the server starts normally.

What I’ve tried (all on Nov 3):

  • Rebooted the app twice
  • Pinned streamlit==1.64.0 (an Oct 23 rebuild had put it on 1.66.1)
  • Changed Python from 3.14 to 3.12 in the app settings
  • Deleted the app and redeployed it to the same subdomain

The hang came back after each change. A headless Chromium running on GitHub Actions times out after 240 seconds on this app. My other two apps on the same account, adaptive-chinese-flashcards and ai-market-pulse, load in about 9 to 13 seconds from the same runner.

The app has no secrets and works on 76 records, so I don’t think it’s running out of memory or CPU.

Could something on the hosting side be stuck for this app? Is there anything else I should try?

2

Thanks for the detailed report—you’ve already ruled out several common causes. My understanding is that the pending, changing JavaScript file isn’t specifically covered by the available troubleshooting docs, so I can’t tell from these sources whether this is a hosting-side fault. The docs do note that persistent loading placeholders can stem from WebSocket/CORS setup, but that guidance is for remotely hosted setups and may not apply to Community Cloud. Remote deployment troubleshooting

Since rebooting and redeploying didn’t resolve it, check Community Cloud status and limitations and use the deployment issues guide to find the relevant support route. Your repo and reproducible symptoms are already useful; including a timestamp and the pending file name from a failed load may help the community compare reports. Would you like more detail?

Sources: