Original request from the customer:
**Steps to Replicate**
1. Open the admin, backed by Solr
2. Browse to a Content Item and click "Edit"
3. Introduce a problem to Solr (so it returns a 500)
4. Hit "Publish"
The admin panel should continue working as the article can be saved to DB. Maybe a user-friendly warning should be issued about Solr failing gracefully.
The admin hangs on an infinite spinner, the content API operation does not complete, and the user is not notified.
Added by Support Team:
I tested it by stopping Solr altogether as a step 3 from steps to reproduce. The result is that after a while the Editor receives message "Could not publish (Connection error : 500.)". This however could still be improved by handling it gracefully and saving the content anyway.