Do not crash the whole SearchKit UI if one entity fails #25433
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Do not crash the whole SearchKit UI if one entity fails
To replicate
civiimport
Before
If one entity is broken the entire SearchKit UI is broken. This can happen when
civiimport
is enabled and an import temp table has been dropped but Managed.reconcile has not yet occurred. I've done a bit of work on trying to prevent this but still see it sometimes & of course a DBA could do it. In addition I've seen it happen with various extension load order issuesAfter
The UI still loads
Technical Details
The class that is being touched is wholly within SearchKit and is a general 'browse' page - I don't think it makes sense to totally fail here when there is a problem
Comments
@colemanw