Task isn’t running and hasn’t stored its results – How to solve this Elasticsearch error

Opster Team

July-20, 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.

Briefly, this error occurs when a task in Elasticsearch is not running and has not stored its results. This can happen if the task was stopped or if there was an error during its execution. To resolve this issue, you can try restarting the task or checking the logs for any 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.

This guide will help you check for common problems that cause the log ” task isn’t running and hasn’t stored its results ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: admin, node, task and cluster.

Log Context

Log “task [{}] isn’t running and hasn’t stored its results”classname  is TransportGetTaskAction.java We extracted the following from Elasticsearch source code for those seeking an in-depth context :

get.setParentTask(clusterService.localNode().getId(); thisTask.getId()); 
 client.get(get; ActionListener.wrap(r -> onGetFinishedTaskFromIndex(r; listener); e -> {
 if (ExceptionsHelper.unwrap(e; IndexNotFoundException.class) != null) {
 // We haven't yet created the index for the task results so it can't be found.
 listener.onFailure(new ResourceNotFoundException("task [{}] isn't running and hasn't stored its results"; e;
 } else {


See how you can use AutoOps to resolve issues

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?

Analyze your cluster & get personalized recommendations

Skip to content