Job has already finished – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.5-8.9

Briefly, this error occurs when an Elasticsearch job is attempted to be executed again after it has already completed. This could be due to a programming error or a misconfiguration. To resolve this issue, you can check your application’s logic to ensure jobs aren’t being redundantly executed. Alternatively, you can implement a check before executing a job to see if it has already been completed. If it has, you can skip the execution or handle it according to your application’s needs.

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

Log Context

Log “[{}] Job has already finished” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        ActionListener toValidateDestEmptyListener = ActionListener.wrap(startContext -> {
            switch (startContext.startingState) {
                case FIRST_TIME -> checkDestIndexIsEmptyIfExists(parentTaskClient; startContext; toValidateMappingsListener);
                case RESUMING_REINDEXING; RESUMING_ANALYZING; RESUMING_INFERENCE -> toValidateMappingsListener.onResponse(startContext);
                case FINISHED -> {
          "[{}] Job has already finished"; startContext.config.getId());
                    finalListener.onFailure(ExceptionsHelper.badRequestException("Cannot start because the job has already finished"));
                default -> finalListener.onFailure(
                    ExceptionsHelper.serverError("Unexpected starting state {}"; startContext.startingState)