[Bug] GitHub API - List workflow runs returns 0 runs even though there are runs

Trying to use the API or the UI to get workflow runs for a specific branch returns no results.

In the UI, when going to Actions on a repo and filtering by branch shows an error message on top of the page We are having problems searching workflow runs. The results may not be complete.

Using the API and the following endpoint:

curl --location --request GET 'https://api.github.com/repos/{owner}/{repo}/actions/workflows/main.yml/runs?branch=my-branch&per_page=1' \
  -H "Authorization: token <my token>" \
  -H "Content-Type: application/vnd.github.v3+json" \

Returns the following even though I can clearly see the run through the pull request UI, or when in the Actions UI and not filtering by branch.

{
  "total_count": 0,
  "workflow_runs": [

  ]
}
7 Likes

I have the same problem on my side in a private repository.

If you call https://api.github.com/repos/{owner}/{repo}/actions/workflows/main.yml/runs without the branch parameter, you can clearly see the runs from that branch in the list.

Also, it seems to work when filtering on older branch, but not on the new ones.

I tried using curl and the octokit from @actions/github.

2 Likes

Am seeing a similar issue, i need the status=in_progress parameter for one of my workflows. Without the filter I can see several workflows with a status of in_progress. The filter for status=completed works as expected. But status=in_progress always returns:

{
  "total_count": 0,
  "workflow_runs": [

  ]
}
1 Like

I get this as well, but only for branches created the last couple of days.
If I use the branch= filter for one of my older branches, it works.

2 Likes

Same problem although with status= filter. Described it here - List workflow runs API not detecting "in_progress" builds - #5 by gat-bryszard

3 Likes

Seems like it’s resolved now

3 Likes

I have a public repo where this is happening. If I list all workflow runs for a workflow without any query parameters, it returns fine. But if I try to query with a parameter, I always get a 404. Currently using the GH CLI, but also happens in GH Actions.

1 Like

I have a similar problem - for example:

curl -i -s -S -H “Accept: application/vnd.github.v3+json” “https://api.github.com/repos/ovsrobot/ovs/actions/runs?branch=series_294442

vs.

curl -i -s -S -H “Accept: application/vnd.github.v3+json” “https://api.github.com/repos/ovsrobot/ovs/actions/runs?branch=series_294634

I am not sure how to proceed

it’s still happening, how is this resolved?

2 Likes

Hello,

I have the same issue on one of my repo, when I list all runs I can see the one I’m looking for :

https://api.github.com/repos/astrelya/REPO/actions/runs”
(I find in the run : head_branch=XXX)

but when I specify the branch

https://api.github.com/repos/astrelya/REPO/actions/runs?branch=XXX”

I get total_count: 0.

EDIT : when I request with parameter actor=astrelya I don’t get all of the runs neither.
EDIT 2 : I checked on other repos, and It seems that I can’t get any run post April 10th by request with parameters.

Thanks.

1 Like

In the GitHub UI, simply filtering (e.g. branch: master) Actions returns empty list with a pink-error banner:

We are having problems searching workflow runs. The results may not be complete.
4 Likes

We are also seeing this. We are getting inconsistent results from filters. An existing query that has not been modified for months is now returning stale data.

3 Likes

We also have the above described problems when using filters.

This bug is marked as solved but it seems to be again open. Is there a way to mark it accordingly here ?

Same here, this started to happen somewhen in the past few days, and caused one of our jobs to go rogue and use up all of our “free” GH action minutes during the night until we could stop it :sob:

Also seeing this issue when querying the workflow runs with a branch name specified. Thus far it has not been working for 3 days.

This is still affecting us, not resolved.

1 Like

I am also having issues still with this endpoint.

When filtering for the branch with ?branch=branch-name I receive

{
  "total_count": 0,
  "workflow_runs": [

  ]
}

However, when I just call the /run endpoint, I can see that the branch that I was filtering for is included in that list. Additionally, there is a red banner on our Github projects when filtering for branches in the actions menu.

We are having problems searching workflow runs. The result may not be complete.

This is what Github support told me:

On Monday, the search functionality with Actions experienced a breaking error. A fix was implemented soon after the break to address the underlying issue, but now search is being re-indexed which can take up to a few days. While this is happening, un-filtered searches for all workflows and specific workflows are working as expected still, but any filtering on those results is broken at this time.

This is impacting filtering both through the UI and API.

We are closely tracking the re-indexing, and I will follow-up here again once it has completed and search is functioning as expected. In the meantime, please let me know if there is anything further you would like to discuss. Thanks!

5 Likes

+1 to this issue

We’re still seeing issues when filtering by branch. We see no results returned in our recently-made repository.

same here:

curl -u m0ppers:$PAT "https://api.github.com/repos/$OWNER/$REPO/actions/workflows/$ID/runs?page=1&per_page=5&branch=master" | jq '.workflow_runs[] | {created_at: .created_at, head_branch: .head_branch}'

returns an 8 day old run as first entry

without branch I get the newer results.

I am using GitHub - dawidd6/action-download-artifact: A GitHub Action to download an artifact associated with given workflow and commit or other criteria to download a terraform plan artifact from a separate workflow and it currently downloads a stale terraform plan and apllying doesn’t work

:upside_down_face: