Paused watch execution; reason ; cancelled queued tasks – 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 ” Paused watch execution; reason ; cancelled queued tasks ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Paused watch execution; reason [{}]; cancelled [{}] queued tasks” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

      * manual watch execution; i.e. via the execute watch API
    public void pauseExecution(String reason) {
        int cancelledTaskCount = executionService.pause();"paused watch execution; reason [{}]; cancelled [{}] queued tasks"; reason; cancelledTaskCount);

     * This reads all watches from the .watches index/alias and puts them into memory for a short period of time;
     * before they are fed into the trigger service.


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content