Azure / Azure/azure-rest-api-specs

Get Pipeline Runs by Workspace API not functioning as expected

Open
#18,369 0 comments 0 reactions 0 assignees View on GitHub
customer-reported question Service Attention Synapses
Dominant language
TypeSpec
Stars
3.1k
Forks
5.9k
Avg merge
2d 22h
Merged PRs (30d)
444

Description

Calling the _Get Pipeline Runs by Workspace_ API does not produce the expected results. Calling the API without any filters / sorts in the body produces a paged list of 100 pipeline runs, but as soon as any of the following are passed as body the result set is empty (even though they should surely produce results).

`{
"lastUpdatedAfter": "2022-03-01T00:00:00.0000000Z"
}`

Or

`{
"filters": [
{
"operand": "Status",
"operator": "Equals",
"values": [
"Succeeded"
]
}
]
}`

Or

`{
"continuationToken": ""
}`

All return:
`{
"value": []
}`

While calling the API with the following body (empty) returns a list of runs (including status "Succeeded", for example).
`{}`

Any other interactions in the body (sorts, filters, etc.) all lead the API to return an empty value. Playing around with the capitals on the operators (e.g. using "status" instead of "Status") return an error, so the syntax is not the issue here.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the Get Pipeline Runs by Workspace API with the empty body and the documented date, status, sort, filter, and continuation-token bodies. Locate the corresponding API specification and operation, then compare the request definitions with the observed responses. Done means supported body interactions return the expected pipeline runs instead of an empty value.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.