Failed to persist watch record – How to solve related issues

Opster Team

Jan-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 ” Failed to persist watch record ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Failed to persist watch record [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                logger.debug("overwrote watch history record [{}]";;
        } catch (InterruptedException | ExecutionException | TimeoutException | IOException ioe) {
            final WatchRecord wr = watchRecord;
            logger.error((Supplier>) () -> new ParameterizedMessage("failed to persist watch record [{}]"; wr); ioe);

    private void deleteTrigger(Wid watcherId) {
        DeleteRequest request = new DeleteRequest(TriggeredWatchStoreField.INDEX_NAME; "doc"; watcherId.value());


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content