Action action not found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-8.9

Briefly, this error occurs when Elasticsearch tries to execute an action that it doesn’t recognize or that doesn’t exist. This could be due to a typo in the action name, or the action might not be available in the current version of Elasticsearch. To resolve this issue, you should first verify the action name and ensure it’s spelled correctly. If the spelling is correct, check the Elasticsearch documentation to ensure the action is available in your current version. If it’s not, you may need to upgrade your Elasticsearch version or find an alternative action.

This guide will help you check for common problems that cause the log ” Action [” + action + “] not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: .

Log Context

Log “Action [” + action + “] not found” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 onRequestReceived(requestId; action);
 final RequestHandlerRegistry reg = (RequestHandlerRegistry) getRequestHandler(action);
 if (reg == null) {
 assert false : action;
 throw new ActionNotFoundTransportException("Action [" + action + "] not found");
 final String executor = reg.getExecutor();
 if (ThreadPool.Names.SAME.equals(executor)) {
 try (var ignored = threadPool.getThreadContext().newTraceContext()) {
 try {


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?