microsoft / microsoft/AL-Go

[Bug]: Finding latest CI/CD Build Link is not interpreted correctly

Open
#2,370 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
PowerShell
Stars
506
Forks
203
Avg merge
4d 22h
Merged PRs (30d)
6

Description

AL-Go version

Developer/Private

Describe the issue

When running the "Publish To Environment" Workflow with version "latest" it will try to get the latest successful CI/CD Build in the last 90 days. It does this by creating a github api link. In our case it tries to create the following link:

https://api.github.com/repos/COUNT-IT-GmbH-Business-Solutions-ERP/CCMS/actions/runs?per_page=100&page=1&exclude_pull_requests=true&status=completed&branch=main&created=>2026-06-18T12:12:42.4686646Z

When calling this link in the browser we get all successful CI/CD runs but the workflow runs in the last 90 days.

However the workflow returns the following:

No successful CICD run found for branch main in repository COUNT-IT-GmbH-Business-Solutions-ERP/CCMS

We think this is because the link is not interpreted correctly. In the logs the link is shown as follows:

Image

As you can see everything after the "=" is not part of the link anymore. Also, when calling this link the result is empty.

Expected behavior

Publish to Environment with version latest creates the correct github api link to retrieve all successful CI/CD builds in the last 90 days

Steps to reproduce

Run Workflow "Publish To Environment" with version "latest"

Additional context (logs, screenshots, etc.)

logs_95037106173.zip

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the Publish to Environment workflow with version latest and inspect the generated GitHub API link in the workflow logs, including logs_95037106173.zip. Trace where the created= query parameter is assembled and passed to the request. Done means the complete date value remains part of the URL and the workflow finds successful main-branch runs from the last 90 days.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, github-actions, powershell
Domain
api, ci-cd, devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
70/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.