Triggered watches could not be deleted failure – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-7.15

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when Elasticsearch fails to delete triggered watches, which are used for alerting and monitoring. This could be due to insufficient permissions, a non-existent watch ID, or a system error. To resolve this, ensure that the user has the necessary permissions to delete watches. Also, verify that the watch ID exists before attempting to delete it. If the problem persists, check the system logs for any underlying issues that might be causing the failure.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” triggered watches could not be deleted {}; failure [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “triggered watches could not be deleted {}; failure [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                        .filter(r -> r.getIndex().startsWith(HistoryStoreField.INDEX_PREFIX))
                        .collect(Collectors.toMap(BulkItemResponse::getId; BulkItemResponse::getFailureMessage));
                    if (triggeredFailures.isEmpty() == false) {
                        String failure = triggeredFailures.values().stream().collect(Collectors.joining("; "));
                        logger.error("triggered watches could not be deleted {}; failure [{}]";
                            triggeredFailures.keySet(); Strings.substring(failure; 0; 2000));
                    if (historyFailures.isEmpty() == false) {
                        String failure = historyFailures.values().stream().collect(Collectors.joining("; "));
                        logger.error("watch history could not be written {}; failure [{}]";


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?

Get expert answers on Elasticsearch/OpenSearch