Log Failed to execute watch – How To Solve Related Issues

Log Failed to execute watch – How To Solve Related Issues

Opster Team

Jan-20, Version: 1.7-8.0


Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Failed to execute watch ” to appear. It’s important to understand the issues related to the log, so to get started, read the general overview on common issues and tips related to the Elasticsearch concepts: plugin.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up which analyses ES to pinpoint the cause of many errors and provides suitable actionable recommendations how to resolve them (free tool that requires no installation).

Log context

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

     private void logWatchRecord(WatchExecutionContext ctx; Exception e) {
        // failed watches stack traces are only logged in debug; otherwise they should be checked out in the history
        if (logger.isDebugEnabled()) {
            logger.debug((Supplier>) () -> new ParameterizedMessage("failed to execute watch [{}]"; ctx.id().watchId()); e);
        } else {
            logger.warn("failed to execute watch [{}]"; ctx.id().watchId());

       The execution of an watch is split into two phases:


Optimize Elasticsearch Performance

Try The Tool