Skip to content

V2 Compatibility Check Logic Can Lead to Non-Closing SQL Database Transactions #10009

@briggs-octo

Description

@briggs-octo

Severity

2 reports

Version

2026.1.11242, 2026.1.11330

Latest Version

None

What happened?

New V2 compatibility check logic can keep SQL database transactions open, leading to downstream performance issues and potentially increased SQL instance disk use.

Reproduction

Must be on a version that contains this logic.

Error and Stacktrace

May see messages similar to the following in the Octopus Server logs:

4/22/2026 9:00:28 PM +00:00 [Warning] Timed out trying to run CompatibilityDetector for "ServerTasks-x" after 430.3163432 seconds.
System.Threading.Tasks.TaskCanceledException: A task was canceled.

More Information

No response

Workaround

Set an OS-level environment variable, OCTOPUS__FeatureToggles__EnableExecutionsV2CompatibilityDetectionFeatureToggle, with a value of false on all Octopus Server nodes to disable this. Disabling this does not change actual execution/functionality, as this is just a compatibility check.

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugThis issue represents a verified problem we are committed to solving

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions