Cannot start task for transform because state was – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 7.5-8.9

Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.

Try OpsGPT now for step-by-step guidance and tailored insights into your Elasticsearch operation.

Briefly, this error occurs when you try to start a data transformation task in Elasticsearch, but the task is in an incompatible state. This could be due to the task already running, failed, or stopped. To resolve this issue, you can check the task’s current state using the Get Transform API. If it’s running, wait for it to finish. If it’s failed, investigate the cause of the failure. If it’s stopped, you may need to restart it using the Start Transform API. Always ensure that the task is in a state that allows it to be started.

For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.

This guide will help you check for common problems that cause the log ” Cannot start task for transform [{}]; because state was [{}] ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin, task.

Log Context

Log “Cannot start task for transform [{}]; because state was [{}]” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 final IndexerState newState = getIndexer().start();
 if ( {
 new ElasticsearchException("Cannot start task for transform [{}]; because state was [{}]"; transform.getId(); newState)


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?