Octopus Server doesn't close SQL connection after AI Recovery Agent completes

[octopus-hideaki]

Severity

Sev-1, multiple instances affected has potential to cause server downtime

Version

Earliest reported 2026.1.11330

Latest Version

I could reproduce the problem in the latest build

What happened?

Multiple self-hosted customers are reporting that Octopus Server is leaving idle SQL transactions open, resulting in large PVS tables and degradation in Octopus Server performance.

We've also identified cloud instances where the DB storage space is nearly full. Similarly, due to a large PVS table.

We believe the culprit is the AI Recovery Agent endpoint failing to close DB connections.

Reproduction

• Enable AI Feature toggle
• Use the AI recovery agent

Error and Stacktrace

--SQL statement left open

SELECT TOP(1) [c].[Id], [c].[JSON]
FROM [Configuration] AS [c]
WHERE [c].[Id] = N'telemetry' AND [c].[Id] = @id

More Information

No response

Workaround

Avoid using AI Recovery Agent
If you are self-hosted:

• Disable AI features by setting the environment variableOCTOPUS_FeatureToggles_AiFeatureToggle=false (Requires restart)

[todthomson]

Customers can work around this issue by temporarily disabling the AI Recovery Agent using the OCTOPUS_FeatureToggles_AiFeatureToggle and then restarting the Octopus Server instance.

We are currently rolling out a fix which will be available for download and installation for Octopus Cloud Platform customers ASAP.

We will report back here once the fix is available for download with the fixed version numbers for 2026.1.x and 2026.2.x. This issue doesn't apply to 2025.4.x (and older) as those versions of Octopus Server do not contain the AI Recovery Agent feature.

[octoreleasebot]

Release Note: Fix: close sql connection for AI Recovery Agent

[todthomson]

Fixed in: 2026.2.12179 (mostly relevant for Octopus Cloud Platform customers).

We are currently rolling this release out through our canary environments, and (presuming everything goes smoothly) we will be rolling this out to all cloud customers (who are on the standard release schedule) in the coming days.

I will report back once all cloud customers (who are on the standard release schedule) have been upgraded.

[todthomson]

Also, we have back ported this fix to 2026.1 and is included in 2026.1.11481 which is already available for download.

This will be relevant for any self-hosted customers on 2026.1 who are using the newly released AI Recovery Agent feature and who have encountered SQL Server PVS (Persistent Version Store) growth causing database file growth on their SQL Server.

[team-builds-bot]

🎉 The fix for this issue has been released in:

Release stream	Release
2026.1	2026.1.11478
2026.2	2026.2.12250
2026.3+	all releases

[todthomson]

This issue does not affect 2025.4.x and older releases.