workflowRunId and requestId in listener logs always 0 as of May 28th 4:41 PM

[swmbuildserver]

Checks

• I've already read https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners-with-actions-runner-controller/troubleshooting-actions-runner-controller-errors and I'm sure my issue is not covered in the troubleshooting guide.
• I am using charts that are officially provided

Controller Version

0.11.0

Deployment Method

Helm

Checks

• This isn't a question or user support case (For Q&A and community support, go to Discussions).
• I've read the Changelog before submitting this issue and I'm sure it's not due to any recently-introduced backward-incompatible changes

To Reproduce

Check logs of type "Updating job info" produced by listener.
They contain json formatted information in LogMessage which contains workflowRunId and requestId.
As of May 28th 4:41PM CET these values always show up as 0 when before they used to contain a valid id.

Describe the bug

The workflowRunId and the requestId shown in log messages produced by the listener are no longer containing valid Ids but are always 0.
This seems not be caused by a code change in the actions-runner-controller repository but rather by a change in the behavior of github.com as it happened suddenly and without any changes of the runner scaleset infrastructure on our side.
Also, the same runnerscaleset infrastructure running against a self hosted GitHub Enterprise instance is still showing the correct values.

Describe the expected behavior

The workflowRunId and requestId given in the json formatted part of listener log messages should contain correct ids, to make it possible to for example build a URL to access the log file for the workflow run.
We are using queries against the listener log files which join the begin message of a workflow run to the end message by joining them on the unique workflowRunId. Currently this does not work anymore.

Additional Context

Log File Queries:
let orgName="swm-dev";
ContainerLogV2
| where TimeGenerated between (datetime(2025-05-28T16:41:00) .. datetime(2025-05-28T17:07:00))
| where LogMessage contains ("Updating job info")
| where parse_json(replace_regex(tostring(LogMessage), @"^[^\{]*", '')).runnerName matches regex (iff(orgName == "dependabot", "dependabot-[a-z0-9]{5}-runner-[a-z0-9]{5}", strcat("arc-runner-set-", orgName, "-[a-z0-9]{5}-runner-[a-z0-9]{5}")))
| project TimeGenerated, tostring(parse_json(replace_regex(tostring(LogMessage), @"^[^\{]*", '')))

showing the moment the problem started occurring:

5/28/2025, 4:41:44.957 PM
{"runnerName":"arc-runner-set-swm-dev-47r2m-runner-dzhh7","ownerName":"swm-dev","repoName":"mvgo-test","workflowRef":"swm-dev/mvgo-test/.github/workflows/integration-test.yml@refs/heads/develop","workflowRunId":15305734658,"jobDisplayName":"setup-and-run-tests (test, false)","requestId":885777}
5/28/2025, 4:41:32.246 PM
{"runnerName":"arc-runner-set-swm-dev-47r2m-runner-qhv8z","ownerName":"swm-dev","repoName":"mvgo-test","workflowRef":"swm-dev/mvgo-test/.github/workflows/integration-test.yml@refs/heads/develop","workflowRunId":15305734658,"jobDisplayName":"setup-and-run-tests (prod, false)","requestId":885776}
5/28/2025, 4:54:01.048 PM
{"runnerName":"arc-runner-set-swm-dev-47r2m-runner-5wztn","ownerName":"swm-dev","repoName":"mvgo-test","workflowRef":"swm-dev/mvgo-test/.github/workflows/integration-test.yml@refs/heads/develop","workflowRunId":0,"jobDisplayName":"","requestId":0}
5/28/2025, 4:54:01.060 PM
{"runnerName":"arc-runner-set-swm-dev-47r2m-runner-v9666","ownerName":"swm-dev","repoName":"mvgo-test","workflowRef":"swm-dev/mvgo-test/.github/workflows/integration-test.yml@refs/heads/develop","workflowRunId":0,"jobDisplayName":"","requestId":0}
5/28/2025, 5:01:19.322 PM
{"runnerName":"arc-runner-set-swm-dev-47r2m-runner-hchcd","ownerName":"swm-dev","repoName":"beauskunftung-workflows","workflowRef":"swm-dev/beauskunftung-workflows/.github/workflows/end2end-test-by-stage.yml@refs/heads/main","workflowRunId":0,"jobDisplayName":"","requestId":0}
5/28/2025, 5:02:27.609 PM
{"runnerName":"arc-runner-set-swm-dev-47r2m-runner-b6l8r","ownerName":"swm-dev","repoName":"ng-backbone-workflows","workflowRef":"swm-dev/ng-backbone-workflows/.github/workflows/ping-status-systemcomponents.yaml@refs/heads/main","workflowRunId":0,"jobDisplayName":"","requestId":0}
5/28/2025, 5:06:57.359 PM
{"runnerName":"arc-runner-set-swm-dev-47r2m-runner-x5nsg","ownerName":"swm-dev","repoName":"beauskunftung-workflows","workflowRef":"swm-dev/beauskunftung-workflows/.github/workflows/end2end-test-by-stage.yml@refs/heads/main","workflowRunId":0,"jobDisplayName":"","requestId":0}
5/28/2025, 5:06:59.462 PM
{"runnerName":"arc-runner-set-swm-dev-47r2m-runner-j2nc7","ownerName":"swm-dev","repoName":"mvgo-test","workflowRef":"swm-dev/mvgo-test/.github/workflows/integration-test.yml@refs/heads/develop","workflowRunId":0,"jobDisplayName":"","requestId":0}

Controller Logs

https://gist.github.com/swmbuildserver/51fc30a9d43b6a7dfed064c30ea5088b#file-gistfile1-txt

Runner Pod Logs

https://gist.github.com/swmbuildserver/02804247e773242789be938ece18d3c2#file-gistfile1-txt

[github-actions]

Hello! Thank you for filing an issue.

The maintainers will triage your issue shortly.

In the meantime, please take a look at the troubleshooting guide for bug reports.

If this is a feature request, please review our contribution guidelines.

[swmbuildserver]

Whatever the internal problem at github.com was, it seems to have been fixed. Again I did not change anything in our setup, but as of June 5th 21:02 CET the correct IDs are back in the logs.
I will close this issue.

Thank you.

[djhughes]

Please can this be reopened.

We are seeing these fields as empty on new workflow runs since approximately 2025-06-09 19:20:00 (UTC).

Re-runs of jobs from before that point do have those fields populated however.

[swmbuildserver]

Yes, please, I agree. I also see the Ids as 0 again and I can confirm the date and time this changed again:

6/9/2025, 7:23:50.375 PM
{"runnerName":"arc-runner-set-swm-dev-l4992-runner-wdxtg","ownerName":"swm-dev","repoName":"mvgo-test","workflowRef":"swm-dev/mvgo-test/.github/workflows/integration-test.yml@refs/heads/develop","workflowRunId":0,"jobDisplayName":"","requestId":0}
6/9/2025, 7:23:50.354 PM
{"runnerName":"arc-runner-set-swm-dev-l4992-runner-9p6tt","ownerName":"swm-dev","repoName":"mvgo-test","workflowRef":"swm-dev/mvgo-test/.github/workflows/integration-test.yml@refs/heads/develop","workflowRunId":0,"jobDisplayName":"","requestId":0}
6/9/2025, 7:15:55.926 PM
{"runnerName":"arc-runner-set-swm-cloud-management-5dxnm-runner-85jbn","ownerName":"swm-cloud-management","repoName":"renovate-bot","workflowRef":"swm-cloud-management/renovate-bot/.github/workflows/renovate-bot.yaml@refs/heads/main","workflowRunId":0,"jobDisplayName":"","requestId":0}
6/9/2025, 7:14:07.629 PM
{"runnerName":"arc-runner-set-swm-win-xkzmk-runner-6bcpt","ownerName":"SWM","repoName":"nis-qgis-replication-administration","workflowRef":"SWM/nis-qgis-replication-administration/.github/workflows/build_windows.yml@refs/pull/5/merge","workflowRunId":132103,"jobDisplayName":"build","requestId":124029}
6/9/2025, 7:13:41.117 PM
{"runnerName":"dependabot-hxkhm-runner-bzj85","ownerName":"SWM","repoName":"ha-as-trendfolger","workflowRef":"SWM/ha-as-trendfolger/dynamic/dependabot/dependabot-updates@refs/heads/main","workflowRunId":132100,"jobDisplayName":"Dependabot","requestId":124028}

It's actually quite baffling as the replies to Rest API Requests for the workflow runs still return the correct IDs. It seems it is just the go sdk which is used for the listener code that is impacted.

[swmbuildserver]

Reopening as problem has resurfaced.

Does not seem to reopen the issue :(