Trying to update state on non-existing task – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch attempts to update the state of a task that doesn’t exist. This could be due to a task being deleted or completed before the update operation. To resolve this issue, you can ensure that tasks are not deleted or completed prematurely. Alternatively, you can implement error handling to catch this exception and handle it appropriately, such as by creating the task if it doesn’t exist or skipping the update operation if the task is not found.

This guide will help you check for common problems that cause the log ” trying to update state on non-existing task {} ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: task, persistent.

Log Context

Log “trying to update state on non-existing task {}” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                    return update(currentState; tasksInProgress.updateTaskState(taskId; taskState));
                } else {
                    if (tasksInProgress.hasTask(taskId)) {
                        logger.warn("trying to update state on task {} with unexpected allocation id {}"; taskId; taskAllocationId);
                    } else {
                        logger.warn("trying to update state on non-existing task {}"; taskId);
                    throw new ResourceNotFoundException("the task with id {} and allocation id {} doesn't exist"; taskId; taskAllocationId);


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?