AL-Go version
9.0
Describe the issue
Summary
The CreateRelease workflow consistently fails at the Determine artifacts for release step with a 502 Bad Gateway originating from DetermineArtifactsForRelease.ps1 line 36. The failure is fully reproducible across many runs over multiple hours.
Environment
- AL-Go-Actions version: v9.0
- AL-Go template: AL-Go-AppSource @ main (templateSha
04f60f74bafd03df919955477c3dd27964fec65c)
- Projects in repo: 12
- Runner:
windows-latest (GitHub-hosted)
- BcContainerHelper: 6.1.14
Error
Enabling Microsoft telemetry...
##[error]Unexpected error when running action. Error Message: The remote server returned an error: (502) Bad Gateway., StackTrace: at , D:\a_actions\microsoft\AL-Go-Actions\v9.0\DetermineArtifactsForRelease\DetermineArtifactsForRelease.ps1: line 36 <- at , D:\a_temp.ps1: line 3 <- at , D:\a_actions\microsoft\AL-Go-Actions\v9.0\Invoke-AlGoAction.ps1: line 21 <- at , D:\a_temp.ps1: line 2 <- at , : line 1
##[error]Process completed with exit code 1.
What we observed
- Failure is deterministic — same error, same line, every run, across many hours.
- Tried
appVersion: latest and appVersion: 27.0.2620.700 (a specific known-good CI/CD build). Both fail identically at the same line.
- Other workflows on the same repo are working normally: CI/CD completes successfully, PR builds complete, custom scripts that download specific artifacts via
/actions/artifacts/{id}/zip work.
- Issue began during a GitHub Actions degradation on 2026-05-15 (mitigated 08:27 UTC per githubstatus). Failure persists hours after the incident was marked resolved.
- The repo has accumulated approximately 71,000 artifacts in its history (most are
expired: true due to shortLivedArtifactsRetentionDays: 1).
- As an experiment, we manually deleted ~1,000 expired artifact entries via the API. The CreateRelease failure still reproduces identically.
Expected behavior
This is blocking a maintenance release. The same workflow has run successfully on this repo in previous weeks with a similar artifact volume.
Steps to reproduce
Run CreateRelease action
Additional context (logs, screenshots, etc.)
AL-Go version
9.0
Describe the issue
Summary
The
CreateReleaseworkflow consistently fails at theDetermine artifacts for releasestep with a502 Bad Gatewayoriginating fromDetermineArtifactsForRelease.ps1line 36. The failure is fully reproducible across many runs over multiple hours.Environment
04f60f74bafd03df919955477c3dd27964fec65c)windows-latest(GitHub-hosted)Error
Enabling Microsoft telemetry...
##[error]Unexpected error when running action. Error Message: The remote server returned an error: (502) Bad Gateway., StackTrace: at , D:\a_actions\microsoft\AL-Go-Actions\v9.0\DetermineArtifactsForRelease\DetermineArtifactsForRelease.ps1: line 36 <- at , D:\a_temp.ps1: line 3 <- at , D:\a_actions\microsoft\AL-Go-Actions\v9.0\Invoke-AlGoAction.ps1: line 21 <- at , D:\a_temp.ps1: line 2 <- at , : line 1
##[error]Process completed with exit code 1.
What we observed
appVersion: latestandappVersion: 27.0.2620.700(a specific known-good CI/CD build). Both fail identically at the same line./actions/artifacts/{id}/zipwork.expired: truedue toshortLivedArtifactsRetentionDays: 1).Expected behavior
This is blocking a maintenance release. The same workflow has run successfully on this repo in previous weeks with a similar artifact volume.
Steps to reproduce
Run CreateRelease action
Additional context (logs, screenshots, etc.)