Skip to content

Update custom executor docs with `step_*`

What does this MR do?

Update custom executor docs with step_*

Why was this MR needed?

The steps that are introduced in !1963 (merged) aren't documented in the custom executor API, so users aren't aware of this feature.

What are the relevant issue numbers?

closes #26481 (closed)

Merge request reports