Open bjarnef opened 2 months ago
Hi there @bjarnef!
Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.
We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.
We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.
Thanks, from your friendly Umbraco GitHub bot :robot: :slightly_smiling_face:
I was able to consistently produce exceptions & failure to display the examine management page by opening one of the index temp files, inserting some random garbage, and re-saving the file.
Obviously this doesn't help figure out what corrupts the index in the first place, but it might be helpful if the aim is to ensure this page continues to function in the event that we have one.
Sometimes one index may be corrupt for various reason like invalid deletion count: https://github.com/Shazwazza/Examine/issues/382
But it would be great if that didn't prevent the indexes from being shows or at least the others, where it would still be possible to rebuild these indexes.
The corrupted index could probably be shown with an error message - it can't show the search and fields, but it could show it failed to read index or similar.
Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)
13.4.1
Bug summary
Sometimes I am noticed something like this in Examine due a corrupt index (also on Umbraco Cloud). Usually it is fixed by removing the index and restarting application.
Specifics
No response
Steps to reproduce
I think I got this locally after editing a document from Luke, by adding a field with a value for a document, but it seemed it added a new document.
Expected result / actual result
I think we could have better error handling so not all indexes fails to show, but perhaps a unhealthy icon? Perhaps it would even be possible to rebuild index from backoffice in this case?
This item has been added to our backlog AB#46503