Task for data frame transform request getId not found – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.2-7.4

Briefly, this error occurs when Elasticsearch cannot find the task for a specific data frame transform. This could be due to the task being deleted, not yet created, or an incorrect task ID being used. To resolve this issue, you can verify the task ID, ensure the task is created before attempting to access it, or check if the task was accidentally deleted. If the task was deleted, you may need to recreate it.

This guide will help you check for common problems that cause the log ” Task for data frame transform [” + request.getId() + “] not found ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: task, plugin, request.

Log Context

Log “Task for data frame transform [” + request.getId() + “] not found” class name is TransportStartDataFrameTransformTaskAction.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 // Either the transform doesn't exist (the user didn't create it yet) or was deleted
 // after the StartAPI executed.
 // In either case; let the user know
 if (tasks.size() == 0) {
 throw new ResourceNotFoundException("Task for data frame transform [" + request.getId() + "] not found");
 }  assert tasks.size() == 1;  boolean allStarted = tasks.stream().allMatch(StartDataFrameTransformTaskAction.Response::isStarted);


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?