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 Check-Up which can resolve issues that cause many errors.

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.

Advanced users might want to skip right to the common problems section in each concept or try running the Check-Up to analyze Elasticsearch configuration and help resolve this error.

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 {


Watch product tour

Watch how AutoOps finds & fixes Elasticsearch problems

Analyze Your Cluster
Skip to content