OctopusDeploy
SQL Timeouts when trying to access Step Templates
Severity
Low - blocks customers but workaround exists
Version
N/A
Latest Version
Not applicable
What happened?
Customers experience a 500 error when trying to view the step templates within a specific space
Reproduction
- Navigate to Library
- Attempt to view Step Templates
- Page perpetually hangs
Error and Stacktrace
Unhandled error on request: "Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
More Information
No response
Workaround
Scale customers to higher DTU usage limit.
[Internal links]
Slack discussion for latest issue - https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1724755840354339
Slack discussion for initial issue - https://octopusdeploy.slack.com/archives/CNHBHV2BX/p1716500498975779
The Octopus engineering team has reviewed this issue.
After careful consideration, we’ve classed this low priority. This means we won’t work on it in the near future.
We prioritize issues based on the number of people affected, the impact type, and available workarounds.
If you’ve encountered this issue and haven’t informed our support team, please email [email protected]. Knowing how many people this issue affects helps us determine its priority.
Three customers have seen this so far, two have needed to be bumped up a DTU tier. The customer running 2024.4.3613 was bumped to S3 DTU and that still has not fixed this issue (all internal links):
https://octopus.zendesk.com/agent/tickets/187454 - Server 2024.1.12401 https://octopus.zendesk.com/agent/tickets/200796 - Cloud 2024.3.10989 https://octopus.zendesk.com/agent/tickets/205690 - Cloud 2024.4.3613
Are we able to take another look into this please as a bit of a higher priority?
Release Note: Improved the performance of loading step template usages when viewing step templates. Note: This change involves a database migration of releases which may take upwards of a few minutes. If you have many releases (over hundreds of thousands), we recommend more aggressive release retention settings for a quicker upgrade.
:tada: The fix for this issue has been released in:
| Release stream | Release |
|---|---|
| 2025.1 | 2025.1.1083 |
| 2025.2+ | all releases |
