> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/install/9.3-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/set-up-the-adaptive-execution-layer-ael/troubleshooting-ael-cp/steps-cannot-run-with-spark-on-ael.md).

# Steps cannot run with Spark on AEL

The following **Flow** category transformation steps do not run with Spark on AEL. When you include one of these steps in a transformation or job with Spark on AEL, the KTR or KJB may fail to execute without logging an error.

* Annotate stream
* Append streams
* Java filter
* Job executor
* Prioritize streams
* Shared dimension
* Single threader

To avoid this issue, do not use these orchestration steps with Spark on AEL. If you need to organize the flow of your PDI transformations with Spark, the best practice is to use the Pentaho Server to orchestrate the KTRs using a Pentaho engine job.

See the **Pentaho Data Integration** document for details on PDI transformations, jobs, steps, and entries.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pentaho.com/install/9.3-install/pentaho-configuration/tasks-to-be-performed-by-an-it-administrator/set-up-the-adaptive-execution-layer-ael/troubleshooting-ael-cp/steps-cannot-run-with-spark-on-ael.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.