You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"ErrorMessage": "Error while executing SQL command in transaction 'http://localhost/api/tasks/?running=False&apikey= 91868cff854142fca39d65b83807bf8f': Incorrect syntax near 'Queued'.\r\nThe command being executed was:\r\nSELECT COUNT(*) FROM dbo.[ServerTask] WHERE ([State] in ('Canceled', 'Failed', 'Success', 'TimedOut' 'Queued'))\r\nSQL Error 102 - Incorrect syntax near 'Queued'.",
Issue appears to be in SQL command, specifically a missing comma between TimedOut and Queued
Selecting for running=True returns a valid response:
This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.
lockbot
locked as resolved and limited conversation to collaborators
Nov 24, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
kind/bugThis issue represents a verified problem we are committed to solving
From: https://help.octopusdeploy.com/discussions/problems/58777
Versions tested: 3.3.19 (client), 3.17.0 (internal testing)
Issue:
http://localhost/api/tasks/?running=False&apikey=
returnsIssue appears to be in SQL command, specifically a missing comma between
TimedOut
andQueued
Selecting for running=True returns a valid response:
The text was updated successfully, but these errors were encountered: