Stored task status for didn t contain any source – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch tries to retrieve the status of a task, but the task status doesn’t contain any source information. This could be due to a bug, a misconfiguration, or a problem with the task itself. To resolve this issue, you could try the following: 1) Check the task configuration and ensure it’s correct. 2) Update or reinstall Elasticsearch to fix potential bugs. 3) Investigate the specific task causing the error, it might be failing or not properly reporting its status.

This guide will help you check for common problems that cause the log ” Stored task status for [{}] didn’t contain any source! ” 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 “Stored task status for [{}] didn’t contain any source!” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 if (false == response.isExists()) {
 listener.onFailure(new ResourceNotFoundException("task [{}] isn't running and hasn't stored its results"; response.getId()));
 if (response.isSourceEmpty()) {
 listener.onFailure(new ElasticsearchException("Stored task status for [{}] didn't contain any source!"; response.getId()));
 try (
 XContentParser parser = XContentHelper.createParser(