nathanwoctopusdeploy
commented
11 months ago Server is incorrectly trying to Cancel the Script running on Tentacle in this scenario. We know Tentacle has not started the script, so can cancel quickly cancel without trying to cancel the script on Tentacle
Octobob
Severity
No response
Version
2024.1.5531
Latest Version
I could reproduce the problem in the latest build
What happened?
When a deployment to a polling tentacle that has recently gone offline is cancelled, then RPC retries may continue to execute until the RPC retry time limit is reached.
Reproduction
At this point, RPC retry messages will continue to stream in, even though we have cancelled.
Error and Stacktrace
No response
More Information
What appears to be happening is that the cancellation is happening correctly.
But since it has gotten past get capabilities, and has called 'start script', it doesn't know if the Tentacle actually received the message or not. So now it has to call Cancel on the Tentacle just in case.
But because the Tentacle is offline, the Cancel RPC call never gets through.
Workaround
No response