Failed to find token from refresh token after all retries – 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 ” Failed to find token from refresh token after all retries ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin and refresh.

Log Context

Log “failed to find token from refresh token after all retries” classname is
We extracted the following from Elasticsearch source code for those seeking an in-depth context :

                 logger.debug("retrying after [{}] back off"; backofTimeValue);
                final Runnable retryWithContextRunnable = client.threadPool().getThreadContext()
                        .preserveContext(() -> findTokenFromRefreshToken(refreshToken; tokensIndexManager; backoff; listener));
                client.threadPool().schedule(retryWithContextRunnable; backofTimeValue; GENERIC);
            } else {
                logger.warn("failed to find token from refresh token after all retries");
        final SecurityIndexManager frozenTokensIndex = tokensIndexManager.freeze();
        if (frozenTokensIndex.indexExists() == false) {


Watch product tour

Try AutoOps to find & fix Elasticsearch problems

Analyze Your Cluster
Skip to content