Job jobId deleted – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 6.8-8.9

Briefly, this error occurs when a specific job, identified by “jobId”, has been deleted from Elasticsearch. This could be due to manual deletion, an automated process, or a system error. To resolve this, you can recreate the job if it was deleted accidentally. If it’s a system error, check the system logs for any anomalies. If it’s an automated process, review the process to prevent unwanted deletions. Always ensure to have a backup of your Elasticsearch jobs to prevent data loss.

This guide will help you check for common problems that cause the log ” Job [” + jobId + “] deleted ” 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 + “] deleted” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        // Step 5. When the job has been removed from the config index; return a response
        // -------
        CheckedConsumer configResponseHandler = jobDeleted -> {
            if (jobDeleted) {
      "Job [" + jobId + "] deleted");
      ; Messages.getMessage(Messages.JOB_AUDIT_DELETED));
            } else {


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?