[Bug]: AL-Go workflows erroring around partner telemetry

[BW-PA]

AL-Go version

8.0

Describe the issue

A few of our workflows have started failing around partner telemetry step. We haven’t changed any settings Japan files since they were working last.

I’ve noticed the issue in our CI/CD workflows across two different repos.

Thinking maybe it was an issue with the AlGo templates themselves I attempted to check if there were any updates available via the check for AL Go updates workflow which errors in the same way at the same partner telemetry area.

I’m on my phone so apologies for the screenshots. But here they are. One from each workflow.

Expected behavior

Workflows to complete without errors

Steps to reproduce

Run either a CI/CD workflow or the Check for Al Go update workflows.

Additional context (logs, screenshots, etc.)

I am running on self hosted runners. Haven’t yet tried on GitHub runners. But they were working last Friday so don’t think the issue is related to the runner.

One of the output statements had GH: (404) so I’m wondering if a resource has gone offline causing these issues…

Will add more info as required when back at my desk tomorrow.

[BW-PA]

Closing this issue as it appears it was caused by an expired GHTokenWorflow. Weird thing was I had updated it just last week in anticipation of it expiring. And it worked fine in another public repo where it was defined as a Repository Secret. The Repos listed in the screenshots above are using an Environment Secret for GHTokenWorkflow, and even with the updated PAT (classic) that worked in the public repos they failed.

After creating another Classic PAT and updating the environment secret they have started working again.

If I get time to try this scenario again to failure I'll open another issue. But for now, since these are our production apps I'm happy to have them working again.