Assignment with id not found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 8.8-8.9

Briefly, this error occurs when Elasticsearch tries to find an assignment with a specific ID, but it doesn’t exist in the cluster. This could be due to a deletion or a misconfiguration. To resolve this issue, you can verify the existence of the assignment ID in your cluster. If it doesn’t exist, you need to create it. If it should exist, check your configuration and ensure that the assignment ID is correctly referenced. Also, ensure that your cluster state is healthy and all nodes are properly communicating.

This guide will help you check for common problems that cause the log ” assignment with id [{}] not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “assignment with id [{}] not found” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 static ClusterState setToStopping(ClusterState clusterState; String deploymentId; String reason) {
 TrainedModelAssignmentMetadata metadata = TrainedModelAssignmentMetadata.fromState(clusterState);
 final TrainedModelAssignment existingAssignment = metadata.getDeploymentAssignment(deploymentId);
 if (existingAssignment == null) {
 throw new ResourceNotFoundException("assignment with id [{}] not found"; deploymentId);
 // If we are stopping; don't update anything
 if (existingAssignment.getAssignmentState().equals(AssignmentState.STOPPING)) {
 return clusterState;


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?