Failed to set forecasts to failed – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.8-8.2

Briefly, this error occurs when Elasticsearch’s machine learning feature tries to update the status of a forecast to “failed”, but encounters an issue. This could be due to a network problem, insufficient permissions, or a problem with the underlying storage. To resolve this, you can check the network connectivity, ensure the user has the correct permissions, and verify the health of the storage system. Additionally, check the Elasticsearch logs for more detailed error messages that can help pinpoint the exact issue.

This guide will help you check for common problems that cause the log ” [{}] failed to set forecasts to failed ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: task, plugin.

Log Context

Log “[{}] failed to set forecasts to failed” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        ActionListener checkSnapshotVersionListener = ActionListener.wrap(
            mappingsUpdate -> jobResultsProvider.setRunningForecastsToFailed(
                ActionListener.wrap(r -> runJob(jobTask; jobState; params); e -> {
                    if (autodetectProcessManager.isNodeDying() == false) {
                        logger.warn(new ParameterizedMessage("[{}] failed to set forecasts to failed"; params.getJobId()); e);
                        runJob(jobTask; jobState; params);
            e -> {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?