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

Opster Team

Aug-23, Version: 7.6-7.6

Briefly, this error occurs when Elasticsearch’s Watcher feature is not properly upgraded. This can happen when the system is updated to a newer version but the Watcher indices are not upgraded accordingly. To resolve this issue, you can run the Watcher upgrade API to update the indices. Alternatively, you can disable the Watcher feature if it’s not in use. Also, ensure that the Elasticsearch version is compatible with the Watcher version to avoid such issues in the future.

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 and 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?