From 446d8a63fb1ce2fef69f8cbb4e4902b5f9a53fb7 Mon Sep 17 00:00:00 2001 From: Keith Massey Date: Wed, 7 May 2025 10:09:24 -0500 Subject: [PATCH] Adding a known issue for watcher during upgrade (#127834) --- docs/release-notes/known-issues.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/release-notes/known-issues.md b/docs/release-notes/known-issues.md index 56b135ea9ff69..c95f2a353bd06 100644 --- a/docs/release-notes/known-issues.md +++ b/docs/release-notes/known-issues.md @@ -27,3 +27,10 @@ This issue will be fixed in a future patch release (see [PR #126990](https://git ``` For information about editing your JVM settings, refer to [JVM settings](https://www.elastic.co/docs/reference/elasticsearch/jvm-settings). + +* Users upgrading from an Elasticsearch cluster that had previously been on a version between 7.10.0 and 7.12.1 may see that Watcher will not start on 9.x. The solution is to run the following commands in Kibana Dev Tools (or the equivalent using curl): + ``` + DELETE _index_template/.triggered_watches + DELETE _index_template/.watches + POST /_watcher/_start + ```