Could not find token document for refresh token – How to solve related issues

Opster Team

Feb-20, Version: 1.7-8.0

Before you begin reading this guide, we recommend you run Elasticsearch Error Check-Up which analyzes 2 JSON files to detect many errors.

To easily locate the root cause and resolve this issue try AutoOps for Elasticsearch & OpenSearch. It diagnoses problems by analyzing hundreds of metrics collected by a lightweight agent and offers guidance for resolving them. Take a self-guided product tour to see for yourself (no registration required).

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: document, plugin and refresh.

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 :

                     ActionListener.wrap(searchResponse -> {
                        if (searchResponse.isTimedOut()) {
                            logger.debug("find token from refresh token response timed out; retrying");
                            maybeRetryOnFailure.accept(invalidGrantException("could not refresh the requested token"));
                        } else if (searchResponse.getHits().getHits().length  1) {
                            onFailure.accept(new IllegalStateException("multiple tokens share the same refresh token"));
                        } else {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content