Handle Aspen connection failures more gracefully #189
Labels
backend
Suspected problem with backend (server or scraper)
enhancement
New feature or request
frontend
Suspected problem with frontend (client-side code in public directory)
When connections to Aspen fail (e.g., because Aspen is down), Aspine's behavior is currently an infinite loading circle with a technical error description on the backend but no indication to the user of what is going on. We should use a
try
/catch
or something similar on the backend to communicate such a situation to the frontend, which should then display an error message along the lines of "Aspen could not be reached" with a suggestion to try again.The text was updated successfully, but these errors were encountered: