Issues icon indicating copy to clipboard operation
Issues copied to clipboard

Health check timeouts can no longer be increased by the PollingRequestMaximumMessageProcessingTimeout configured on the tentacle.

Open LukeButters opened this issue 2 years ago • 0 comments

Severity

No response

Version

2024.1.8781

Latest Version

None

What happened?

The changes for issue: https://github.com/OctopusDeploy/Issues/issues/8118 added a health check timeout which is partially controlled by the Polling Response Timeout. That Polling Response Timeout is toggled off in https://github.com/OctopusDeploy/Issues/issues/8578. This means that customers can not configure that timeout, and so have one less way of configuring the overall health check timeout.

When the Polling Response Timeout is actually removed the total timeout of the health check will decrease by the previous PollingResponseTimeout.

Reproduction

It can't be done.

Error and Stacktrace

No response

More Information

No response

Workaround

No response

LukeButters avatar Jan 29 '24 02:01 LukeButters