Could not find token document for refresh token – How to solve this Elasticsearch error

Opster Team

Aug-23, Version: 7.2-8.9

Briefly, this error occurs when Elasticsearch cannot locate the document associated with a specific refresh token. This could be due to the document being deleted, or the token has expired. To resolve this issue, you can try the following: 1) Ensure the document associated with the token hasn’t been deleted. 2) Check the token’s expiration date and renew it if necessary. 3) If the problem persists, consider generating a new refresh token.

This guide will help you check for common problems that cause the log ” could not find token document for refresh token ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, refresh, document.

Log Context

Log “could not find token document for refresh token” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

        final Instant refreshRequested = clock.instant();
        final Iterator backoff = DEFAULT_BACKOFF.iterator();
        final Consumer onFailure = ex -> listener.onFailure(traceLog("find token by refresh token"; refreshToken; ex));
        findTokenFromRefreshToken(refreshToken; backoff; ActionListener.wrap(searchHits -> {
            if (searchHits.getHits().length  1) {
                onFailure.accept(new IllegalStateException("multiple tokens share the same refresh token"));
            } else {
                final SearchHit tokenDocHit = searchHits.getAt(0);