Deleted forecasts from job – How to solve related issues

Average Read Time

2 Mins

Deleted forecasts from job – 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 can resolve issues that cause many errors.

This guide will help you check for common problems that cause the log ” Deleted forecasts from job ” 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: delete and 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 “Deleted forecast(s) [{}] from job [{}]” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                     Tuple statusAndReason = getStatusAndReason(response);
                        new ElasticsearchStatusException(statusAndReason.v2().getMessage(); statusAndReason.v1(); statusAndReason.v2()));
      "Deleted forecast(s) [{}] from job [{}]"; forecastIds; jobId);
                listener.onResponse(new AcknowledgedResponse(true));


Run the Check-Up to get a customized report like this:

Analyze your cluster