V2 execution pipeline can cause deployments to show "pending" in the task logs and proceed no further

[donnybell]

Severity

Blocking when encountered

Version

Discovered in 2025.4.1893

Latest Version

None

What happened?

With the V2 execution pipeline enabled, a task was only showing Pending: in the logs after the initial header information. The task did not proceed and would likely have remained "stuck" until cancelled.

Reproduction

Exact reproduction steps unclear. Disabling V2 execution pipelines for the instance restored normal operation.

See discussion here [internal link]

Error and Stacktrace

More Information

No response

Workaround

Disable v2 execution pipelines according to the instructions in the rollback plan [internal link]