[CI] Remote machine provider fails to connect an agent within 45 minutes

[dalexsoto]

Failure signature

Azure jobs are canceled before any task starts with:

Remote machine provider issue: The agent did not connect within the alloted time of 45 minute(s).

Confirmed occurrences

PR / head	Build and job	Outcome
#26203 / abd0ea0058d6285dccbdcc9c0fc4837d264b45d0	14718863 - arm64 Mac Golden Gate (27)	No agent connected within 45 minutes. The separately accepted stage attempt 2 succeeded.
#26131 / 067c0f36f6aed495bc0b54f4cebe08ca41e9e0bb	14731458 - linker_maccatalyst	No agent connected; build remains active, so no retry has been submitted.

First observed: 2026-07-21 19:22 UTC. Latest observed: 2026-07-22 13:55 UTC. Recurrence: 2 jobs across 2 distinct monitored PRs.

Classification and impact

This is a CI infrastructure failure in the remote machine provider. The affected job never receives a worker and executes no repository task, so otherwise unrelated PRs are blocked by a terminal canceled check.

Investigation

• Inspected the Azure timeline records and exact job issues for both builds.
• Confirmed the current [src] Clean/consolidate runtime initialization code between platforms. #26131 job has no worker name, task logs, or executed child tasks.
• Confirmed the [NearbyInteraction] Update bindings up to Xcode 27.0 Beta 3 #26203 retry succeeded, demonstrating that the source/build was not the cause.
• Searched all open and closed dotnet/macios issues using the exact message, Remote machine provider issue, the 45-minute text, and AcesShared terminology; no matching issue was found.

Workaround

After the build is terminal, the PR is conflict-free, retry accounting is reconciled, and no equivalent attempt is active, rerun the failed job/stage. Azure diagnostic artifacts and timelines have limited retention.

[dalexsoto]

New affected PR: #26235 @ 2d6de8eae3de15bb792cf87f872078184a018c43, build 14731906, job arm64 Mac Golden Gate (27). The remote machine provider did not connect an agent within the allotted 45 minutes; no repository task ran.

The signature now affects 3 jobs across 3 monitored PRs. Build 14731906 remains active, so no retry has been submitted.

[dalexsoto]

External retry update for #26235 @ 2d6de8eae3de15bb792cf87f872078184a018c43: build 14731906 mac_27_arm64 attempt 2 was queued around 15:55 UTC to rerun the Mac Golden Gate job. No retry was initiated by this monitor.

[dalexsoto]

Retry update for #26131 @ 067c0f3660d7f7b37946067d327650bd298bf524: build 14731458 simulator_tests attempt 2 was accepted at 16:24 UTC to rerun linker_maccatalyst together with three other infrastructure-failed jobs. Reconciled budget is 2 lifetime / 1 current-head request.

[dalexsoto]

Retry outcome for #26235: build 14731906 mac_27_arm64 attempt 2 again failed because the remote machine provider did not connect an agent within 45 minutes; no repository task ran. This is a new occurrence, bringing the signature to 4 jobs across 3 monitored PRs.

An external mac_27_arm64 attempt 3 is now in progress and has been assigned to AcesShared 6; no retry was initiated by this monitor. Authoritative GitHub PR and Azure trigger metadata report head 2d6de8eaf12aff5c2f4bff984ce5085b1fece6f7, correcting the different full SHA in the earlier comments for this same build.

[dalexsoto]

Retry outcome for #26235 @ 2d6de8eaf12aff5c2f4bff984ce5085b1fece6f7: build 14731906 mac_27_arm64 attempt 3 completed successfully on AcesShared 6. The full build succeeded at 19:52 UTC, and the PR merged immediately afterward.

The recurrence count remains 4 jobs across 3 monitored PRs; this successful retry further confirms the remote-machine-provider classification rather than a source failure.

[dalexsoto]

Three new monitored PRs hit the same infrastructure signature in SDL Sources Analysis (self): the remote machine provider did not connect an agent within 45 minutes, and no repository task ran.

• [net11.0] Update dependencies from dotnet/dotnet #26356 @ 33331032bfa97193b925ef4310a7f10a1511383d: build 14957447, attempt 1, canceled at 2026-08-13 02:49 UTC. Azure API retry attempt 2 is queued.
• [release/10.0.1xx] Update dependencies from dotnet/dotnet #26443 @ 76abb5bcaa11fd4dedb414f859229b352ef08691: build 14957448, attempt 1, canceled at 2026-08-13 02:49 UTC. Azure API retry attempt 2 is queued.
• [main] Update dependencies from dotnet/dotnet #26444 @ a117ce0ef8f74c17bdd0ebdd2989e1bf1a49b713: build 14957456, attempt 1, canceled at 2026-08-13 02:50 UTC. Azure API retry attempt 2 is queued.

Classification: CI infrastructure failure. The stable signature now has 7 confirmed job occurrences across 6 distinct monitored PRs. The issue has no Additional info to collect checklist.

[dalexsoto]

Retry outcome for the three new SDL Sources Analysis (self) occurrences: attempt 2 reproduced the same infrastructure failure in every PR — Remote machine provider issue: The agent did not connect within the alloted time of 45 minute(s). No repository task ran.

• [net11.0] Update dependencies from dotnet/dotnet #26356 @ 33331032bfa97193b925ef4310a7f10a1511383d: build 14957447, attempt 2, completed canceled around 2026-08-13 03:39 UTC. Azure API attempt 3 is queued.
• [release/10.0.1xx] Update dependencies from dotnet/dotnet #26443 @ 76abb5bcaa11fd4dedb414f859229b352ef08691: build 14957448, attempt 2, completed canceled around 2026-08-13 03:39 UTC. Azure API attempt 3 is queued.
• [main] Update dependencies from dotnet/dotnet #26444 @ a117ce0ef8f74c17bdd0ebdd2989e1bf1a49b713: build 14957456, attempt 2, completed canceled around 2026-08-13 03:39 UTC. Azure API attempt 3 is queued.

Classification remains CI infrastructure failure. Including the prior issue history, the stable signature now has 10 confirmed job occurrences across 6 distinct monitored PRs. The issue has no Additional info to collect checklist.

[dalexsoto]

Retry outcome for the three SDL Sources Analysis (self) occurrences: attempt 3 again reproduced the same CI infrastructure failure — Remote machine provider issue: The agent did not connect within the alloted time of 45 minute(s). No repository task ran.

• [net11.0] Update dependencies from dotnet/dotnet #26356 @ 33331032bfa97193b925ef4310a7f10a1511383d: build 14957447, attempt 3, completed canceled at 2026-08-13 04:28 UTC. Azure API attempt 4 is queued.
• [release/10.0.1xx] Update dependencies from dotnet/dotnet #26443 @ 76abb5bcaa11fd4dedb414f859229b352ef08691: build 14957448, attempt 3, completed canceled at 2026-08-13 04:28 UTC. Azure API attempt 4 is queued.
• [main] Update dependencies from dotnet/dotnet #26444 @ a117ce0ef8f74c17bdd0ebdd2989e1bf1a49b713: build 14957456, attempt 3, completed canceled at 2026-08-13 04:28 UTC. Azure API attempt 4 is queued.

Classification remains CI infrastructure failure. Including prior issue history, the signature now has 13 confirmed job occurrences across 6 distinct monitored PRs. The issue has no Additional info to collect checklist.

[dalexsoto]

Retry outcome for the three SDL Sources Analysis (self) occurrences: attempt 4 again reproduced the same CI infrastructure failure — Remote machine provider issue: The agent did not connect within the alloted time of 45 minute(s). No repository task ran.

• [net11.0] Update dependencies from dotnet/dotnet #26356 @ 33331032bfa97193b925ef4310a7f10a1511383d: build 14957447, attempt 4, completed canceled at 2026-08-13 05:20 UTC. Azure API attempt 5 is queued.
• [release/10.0.1xx] Update dependencies from dotnet/dotnet #26443 @ 76abb5bcaa11fd4dedb414f859229b352ef08691: build 14957448, attempt 4, completed canceled at 2026-08-13 05:20 UTC. Azure API attempt 5 is queued.
• [main] Update dependencies from dotnet/dotnet #26444 @ a117ce0ef8f74c17bdd0ebdd2989e1bf1a49b713: build 14957456, attempt 4, completed canceled at 2026-08-13 05:20 UTC. Azure API attempt 5 is queued.

Classification remains CI infrastructure failure. Including prior issue history, the signature now has 16 confirmed job occurrences across 6 distinct monitored PRs. The issue has no Additional info to collect checklist.

[dalexsoto]

Retry outcome for the three SDL Sources Analysis (self) occurrences: attempt 5 again reproduced the same CI infrastructure failure — Remote machine provider issue: The agent did not connect within the alloted time of 45 minute(s). No repository task ran.

• [net11.0] Update dependencies from dotnet/dotnet #26356 @ 33331032bfa97193b925ef4310a7f10a1511383d: build 14957447, attempt 5, completed canceled at 2026-08-13 06:11 UTC. Azure API attempt 6 is reserved.
• [release/10.0.1xx] Update dependencies from dotnet/dotnet #26443 @ 76abb5bcaa11fd4dedb414f859229b352ef08691: build 14957448, attempt 5, completed canceled at 2026-08-13 06:11 UTC. Azure API attempt 6 is reserved.
• [main] Update dependencies from dotnet/dotnet #26444 @ a117ce0ef8f74c17bdd0ebdd2989e1bf1a49b713: build 14957456, attempt 5, completed canceled at 2026-08-13 06:11 UTC. Azure API attempt 6 is reserved.

Classification remains CI infrastructure failure. The monitor ledger now contains 15 confirmed occurrences across 3 distinct currently monitored PRs; including the prior issue history, this is 19 confirmed job occurrences across 6 distinct PRs. The issue has no Additional info to collect checklist.

[dalexsoto]

Retry outcome for the three SDL Sources Analysis (self) occurrences: attempt 6 again reproduced the same CI infrastructure failure — Remote machine provider issue: The agent did not connect within the alloted time of 45 minute(s). No repository task ran.

• [net11.0] Update dependencies from dotnet/dotnet #26356 @ 33331032bfa97193b925ef4310a7f10a1511383d: build 14957447, attempt 6, completed canceled at 2026-08-13 06:59 UTC. Azure API attempt 7 is reserved.
• [release/10.0.1xx] Update dependencies from dotnet/dotnet #26443 @ 76abb5bcaa11fd4dedb414f859229b352ef08691: build 14957448, attempt 6, completed canceled at 2026-08-13 06:59 UTC. Azure API attempt 7 is reserved.
• [main] Update dependencies from dotnet/dotnet #26444 @ a117ce0ef8f74c17bdd0ebdd2989e1bf1a49b713: build 14957456, attempt 6, completed canceled at 2026-08-13 06:59 UTC. Azure API attempt 7 is reserved.

Classification remains CI infrastructure failure. The monitor ledger now contains 18 confirmed occurrences across 3 distinct currently monitored PRs; including prior issue history, this is 22 confirmed job occurrences across 6 distinct monitored PRs. The issue has no Additional info to collect checklist.