Watch history could not be written . failure – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

This guide will help you check for common problems that cause the log ” Watch history could not be written . failure ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: shard.

Log Context

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

                         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 [{}]";
                            historyFailures.keySet(); Strings.substring(failure; 0; 2000));

                    Map overwrittenIds =


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content