Not starting watcher upgrade API run required watches triggered watches – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.15

Briefly, this error occurs when Elasticsearch’s Watcher feature, which is used for alerting and notification based on changes in data, is not properly upgraded. This could be due to an incomplete upgrade process or a version mismatch. To resolve this issue, you can try the following: 1) Ensure that the Elasticsearch version is compatible with the Watcher version. 2) Run the Watcher upgrade API to update the Watcher to the latest version. 3) Check the Elasticsearch logs for any additional errors that might indicate the root cause of the problem.

This guide will help you check for common problems that cause the log ” not starting watcher; upgrade API run required: .watches[{}]; .triggered_watches[{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, upgrade.

Log Context

Log “not starting watcher; upgrade API run required: .watches[{}]; .triggered_watches[{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        boolean isIndexInternalFormatWatchIndex = watcherIndexMetadata == null ||
        boolean isIndexInternalFormatTriggeredWatchIndex = triggeredWatchesIndexMetadata == null ||
        if (isIndexInternalFormatTriggeredWatchIndex == false || isIndexInternalFormatWatchIndex == false) {
            logger.warn("not starting watcher; upgrade API run required: .watches[{}]; .triggered_watches[{}]";
                isIndexInternalFormatWatchIndex; isIndexInternalFormatTriggeredWatchIndex);
            return false;

        try {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?