Job jobId does not exist – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-6.8

Briefly, this error occurs when Elasticsearch tries to access a job with a specific ID, but it can’t find it. This could be due to the job being deleted, not yet created, or a typo in the job ID. To resolve this issue, you can verify the job ID, ensure the job has been created before trying to access it, or check if the job was accidentally deleted. If the job was deleted, you may need to recreate it.

This guide will help you check for common problems that cause the log ” job [” + jobId + “] does not exist ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “job [” + jobId + “] does not exist” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 throw ExceptionsHelper.conflictStatusException("Unexpected job state [" + jobState + "]; expected [" +
 JobState.CLOSED + " or " + JobState.FAILED + "]");
 Job job = jobs.remove(jobId);
 if (job == null) {
 throw new ResourceNotFoundException("job [" + jobId + "] does not exist");
 if (job.isDeleting() == false) {
 throw ExceptionsHelper.conflictStatusException("Cannot delete job [" + jobId + "] because it hasn't marked as deleted");
 return this;


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?