dudahl
June 17, 2025, 5:53pm
18
Hello @stephenb , thx for the answer!!
I did what you said and got the following result:
{
"statusCode": 400,
"error": "Bad Request",
"message": "Error injecting reference into rule params for rule id 4fcb9f70-8014-11ee-b50b-0b6b99edc1f - Could not find reference for kibanaSavedObjectMeta.searchSourceJSON.index"
}
searched a little bit more and found two links that may be helpful, even though the first one was closed without resolution:
Hi,
After playing around with alerting and browser monitors in uptime, my alert rules page got completely broken. On every request it raises an error similar to:
Could not find reference for kibanaSavedObjectMeta.searchSourceJSON.index
These errors provide saved object IDs which point to the alerts I've tried to silence right before everything broke down.
Is it possible to somehow reanimate/delete alert in this state? So far I've tried the saved objects UI and the API. The UI says there's a …
and
opened 08:19PM - 08 Mar 23 UTC
bug
Feature:Alerting
Team:ResponseOps
Feature:Alerting/RuleTypes
**stack version:** 8.6.2
User is getting a 400 from the `/internal/alerting/r… ules/_find` route with the error message
Error injecting reference into rule params for rule id <id> -
Could not find reference for kibanaSavedObjectMeta.searchSourceJSON.index
Looking the rule saved object, the `references` array is empty, but there are indirect references to two expected references in the remaining body of the saved object. So it looks like somehow the references were removed from the saved object.
That by itself is obviously not good, but the real problem is the 400 from the `_find` call causes the rule list to be displayed empty, when that rule would be in the list. Regardless of internal difficulties with the rule objects, they shouldn't prevent the rule list from being displayed.
Looks like this may be a changed in behavior in 8.6.2 from 8.5.3. Previously, the user saw 2 "unable to load rule" toasts when displaying rules, but since the upgrade, they only see 1, but also now don't see any rules at all. Presumably there is some other rule with an error (the remaining toast).