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

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when you try to retrieve the results of a task in Elasticsearch that either isn’t running or hasn’t stored its results yet. This could be due to the task being cancelled, failed, or not started at all. To resolve this issue, you can check the task’s status using the Task Management API. If the task isn’t running, you may need to restart it. If it hasn’t stored its results, you may need to wait for it to complete or check if there’s an issue preventing it from storing results.

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, cluster.

Log Context

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

 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.
 new ResourceNotFoundException("task [{}] isn't running and hasn't stored its results"; e; request.getTaskId())
 } else {