Cannot run forecast: internal error; please check the logs – How to solve this Elasticsearch error

Opster Team

March-22, Version: 1.7-8.0

Before you begin reading this guide, we recommend you try running the Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many configuration 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 ” Cannot run forecast: internal error; please check the logs ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “Cannot run forecast: internal error; please check the logs”classname  is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

private void getForecastRequestStats(String jobId; String forecastId; ActionListener listener) {
 Consumer forecastRequestStatsHandler = forecastRequestStats -> {
 if (forecastRequestStats == null) {
 // paranoia case; it should not happen that we do not retrieve a result
 listener.onFailure(new ElasticsearchException("Cannot run forecast: internal error; please check the logs"));
 } else if (forecastRequestStats.getStatus() == ForecastRequestStats.ForecastRequestStatus.FAILED) {
 List messages = forecastRequestStats.getMessages();
 if (messages.size() > 0) {
 String message = messages.get(0);


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content