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

Opster Team

Aug-23, Version: 6.8-7.1

Briefly, this error occurs when Elasticsearch is unable to locate a document associated with a specific refresh token. This could be due to the token being expired, deleted, or never existed. To resolve this issue, you can try the following: 1) Ensure the token is correctly inputted and hasn’t expired. 2) If the token is expired, you need to generate a new one. 3) Check your Elasticsearch logs for any related issues. 4) If the token was deleted, you may need to recreate the document it was associated with.

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

Log Context

Log “could not find token document with 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()) {
                                findTokenFromRefreshToken(refreshToken; listener; attemptCount);
                            } else if (searchResponse.getHits().getHits().length  1) {
                                onFailure.accept(new IllegalStateException("multiple tokens share the same refresh token"));
                            } else {
                                listener.onResponse(new Tuple(searchResponse; attemptCount));


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?