"Waiting for the script in task X to finish" can reference an ID with no corresponding task

[Rose-Northey]

Severity

There's a workaround but it leaves users with no way to identify what's actually stuck

Version

2026.2.12018

Latest Version

Not applicable

What happened?

When a deployment or runbook run is blocked waiting for another script to finish on the same target/worker, Octopus shows a message like "Waiting for the script in task to finish". The intent is for to be the ServerTask (or RunbookRun) ID holding the lock, so you can click through and find out what's blocking you.

The id doesn't correspond to any real task. There's no way to trace it back and find out what's actually blocking the deployment.

Reproduction

1. Run a deployment/runbook that executes a script against a target or worker.
2. While that script is running (or stuck/cancelled but not yet released - see Workaround), trigger a second deployment/runbook against the same target/worker.
3. The second task's log shows "Waiting for the script in task to finish", where is a short alphanumeric string rather than a ServerTasks-NNN / RunbookRuns-NNN ID.

Error and Stacktrace

Waiting for the script in task XXXXXX to finish

More Information

No response

Workaround

If a task appears permanently stuck, removing and re-adding the affected worker/target, or restarting the Tentacle, releases the stuck lock so new tasks can proceed.