# Error loading execution history for alert rules

**URL:** <https://discuss.elastic.co/t/error-loading-execution-history-for-alert-rules/329774>\
**Category:** Elastic Observability\
**Created:** [April 11, 2023, 7:01pm UTC](https://discuss.elastic.co/t/error-loading-execution-history-for-alert-rules/329774 "2023-04-11T19:01:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Landorks](https://avatars.discourse-cdn.com/v4/letter/l/34f0e0/32.png) [@Landorks](https://discuss.elastic.co/u/Landorks)\
**Post date:** [April 11, 2023, 7:01pm UTC](https://discuss.elastic.co/t/error-loading-execution-history-for-alert-rules/329774/1 "2023-04-11T19:01:45Z")

</div>

Hi,  
I get the following error in Kibana (8.4.3) when trying to view an alert. It appears that this is causing alerts not to fire at all. Everything was working fine about a week ago. I've already tried creating a new alert but get the same error. Any ideas on how I can resolve this?

```auto
Failed to fetch execution history
An internal server error occurred. Check Kibana server logs for details.

```

Kibana logs show

```auto
[kibana.log][ERROR] querying for Event Log by for type "alert" and ids "d6907520-d6a6-11ed-a68e-4d6633f6e8a9" failed with: search_phase_execution_exception: [query_shard_exception] Reason: failed to create query: [nested] failed to find nested object under path [kibana.saved_objects]
Error: querying for Event Log by for type "alert" and ids "d6907520-d6a6-11ed-a68e-4d6633f6e8a9" failed with: search_phase_execution_exception: [query_shard_exception] Reason: failed to create query: [nested] failed to find nested object under path [kibana.saved_objects]
    at ClusterClientAdapter.aggregateEventsBySavedObjects (/usr/share/kibana/x-pack/plugins/event_log/server/es/cluster_client_adapter.js:382:13)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at EventLogClient.aggregateEventsBySavedObjectIds (/usr/share/kibana/x-pack/plugins/event_log/server/event_log_client.js:104:12)
    at RulesClient.getExecutionLogForRule (/usr/share/kibana/x-pack/plugins/alerting/server/rules_client/rules_client.js:517:25)
    at /usr/share/kibana/x-pack/plugins/alerting/server/routes/get_rule_execution_log.js:115:13
    at /usr/share/kibana/x-pack/plugins/alerting/server/routes/lib/verify_access_and_context.js:27:14
    at /usr/share/kibana/node_modules/@kbn/core-http-router-server-internal/target_node/error_wrapper.js:22:14
    at Router.handle (/usr/share/kibana/node_modules/@kbn/core-http-router-server-internal/target_node/router.js:163:30)
    at handler (/usr/share/kibana/node_modules/@kbn/core-http-router-server-internal/target_node/router.js:124:50)
    at exports.Manager.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
    at Object.internals.handler (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:46:20)
    at exports.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:31:20)
    at Request._lifecycle (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:371:32)
    at Request._execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:281:9)

```

---

<div class="post-metadata">

**Author:** ![ERASMO\_BORGES\_DA\_SIL](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/erasmo_borges_da_sil/32/123433_2.png) [@ERASMO\_BORGES\_DA\_SIL](https://discuss.elastic.co/u/ERASMO_BORGES_DA_SIL)\
**Post date:** [July 13, 2023, 4:30pm UTC](https://discuss.elastic.co/t/error-loading-execution-history-for-alert-rules/329774/2 "2023-07-13T16:30:40Z")

</div>

I have the same problem...

Did you manage to solve the problem?

---

<div class="post-metadata">

**Author:** ![Landorks](https://avatars.discourse-cdn.com/v4/letter/l/34f0e0/32.png) [@Landorks](https://discuss.elastic.co/u/Landorks)\
**Post date:** [July 13, 2023, 7:47pm UTC](https://discuss.elastic.co/t/error-loading-execution-history-for-alert-rules/329774/3 "2023-07-13T19:47:34Z")

</div>

I never did get an official answer but I was able to get it working by deleting the .kibana-event-log-8.4.3 indices