SQL error when querying for a task with >2100 tasks with the same concurrency tag (2100 parameter limit)

[susanpann]

Severity

SEV3 - Low

Version

Reported on 2023.2.13239

Latest Version

None

What happened?

UI blocked when viewing a task with >2100 tasks with the same concurrency tag

Reproduction

Error and Stacktrace

2023-11-06 12:25:30.0153   7012    315 ERROR  Unhandled error on request: "Error while executing SQL command in transaction 'GetBlockingTasks.GetBlockingTasks|800197e9-0000-da00-b63f-84710c7967bb|T371': The incoming request has too many parameters. The server supports a maximum of 2100 parameters. Reduce the number of parameters and resend the request.
The command being executed was:
SELECT Id,Created,Title,Status,RelatedDocumentIds,ResponsibleTeamIds,ProjectId,TenantId,EnvironmentId,TaskId,SpaceId,BlockConcurrentTasks,Type,LastModified,DataVersion,JSON
FROM [dbo].[Interruption]
WHERE (((([SpaceId] in ('Spaces-1', 'Spaces-2', 'Spaces-22')) AND 1=0) OR (([SpaceId] in ('Spaces-3')))))
AND ([BlockConcurrentTasks] = @p1)
AND ([TaskId] IN (@p2, @p3, @p4, @p5, @p6, @p7, @p8, @p9, @p10, @p11, @p12, @p13, @p14, @p15, @p16, @p17, @p18, @p19, @p20, @p21, @p22, @p23, @p24, @p25, @p26, @p27, @p28, @p29, @p30, @p31, @p32, @p33, @p34, @p35, @p36, @p37, @p38, @p39, @p40, @p41, @p42, @p43, @p44, @p45, @p46, @p47, @p48, @p49, @p50, @p51, @p52, @p53, @p54, @p55, @p56, @p57, @p58, @p59, @p60, @p61, @p62, @p63, @p64, @p65, @p66, @p67, @p68, @p69, @p70, @p71, @p72, @p73, @p74, @p75, @p76, @p77, @p78, @p79, @p80, @p81, @p82, @p83, @p84, @p85, @p86, @p87, @p88, @p89, @p90, @p91, @p92, @p93, @p94, @p95, @p96, @p97, @p98, @p99, @p100, @p101, @p102, @p103...

More Information

https://github.com/OctopusDeploy/OctopusDeploy/blob/a89469fa65c61d49a53f3842750e091c784b3bb5/source/Octopus.Core/Model/ServerTasks/BlockingTaskService.cs#L69

Workaround

No response

[michelle-luana]

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.

[KennethBates]

Another instance of this issue: https://octopus.zendesk.com/agent/tickets/251802