Log Triggered watches could not be deleted ; failure – How To Solve Related Issues

Log Triggered watches could not be deleted ; failure – How To Solve Related Issues

Updated: Jan-20

Elasticsearch Version: 1.7-8.0


To resolve issues causing many log errors you can try our Elasticsearch Check-Up it analyses ES configuration to provide actionable recommendations (no installation required) 

To troubleshoot log “Triggered watches could not be deleted ; failure” it’s important to understand a few problems related to Elasticsearch concepts plugin. See bellow important tips and explanations on these concepts

Log Context

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

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

                    Map overwrittenIds = Arrays.stream(response.getItems())

Related issues to this log

We have gathered selected Q&A from the community and issues from Github, that can help fix related issues please review the following for further information :

1 Illegal State Exception Is Preventi  

Github Issue Number 40053  


About Opster

Opster detects, resolves, optimizes, automates and prevents incidents in Elasticsearch. Opster’s line of products delivers a fundamentally more effective Elasticsearch operation and backs it up with superb production support and consulting.

Find Configuration Errors

Analyze Now