P.S.A. Increase failure rate with Internal Errors

We've seen an increased failure rate with Internal Errors.
I had my agent run an investigation and the results are below.

We have filed an incident with our infrastructure provider.

---

Confirmed. There is a broad dynamic-scan incident, but the evidence does not yet prove the GitHub App caused it.

• GitHub App production cutover: August 10, 20:10 UTC — https://github.com/microsoft/winget-pkgs/issues/263724
• 231 PRs currently carry  Internal-Error-Dynamic-Scan .
• In a measured August 12 window, 69 of 209 new PRs—33%—were affected. This is conservative because later validations were still running.
• The failures span many packages and contributors, not just the reporter.
• The reporter’s post-cutover series had 3 of 10 PRs affected, including both 1.32 packages:
• https://github.com/microsoft/winget-pkgs/pull/416226
• https://github.com/microsoft/winget-pkgs/pull/416227
• https://github.com/microsoft/winget-pkgs/pull/415912
• Unrelated examples show the same signature:
• https://github.com/microsoft/winget-pkgs/pull/416070
• https://github.com/microsoft/winget-pkgs/pull/416388

The App exposes the validation stages as GitHub checks; dynamic scanning itself predates the migration, and similar infrastructure errors were already tracked at https://github.com/microsoft/winget-pkgs/issues/411157. My conclusion is confirmed high failure rate and likely dynamic-scan infrastructure/capacity failure coincident with the cutover—not confirmed App regression.

Start with the prior incident in issue 411157 and the GitHub checks and pull requests listed here. Compare the Internal-Error-Dynamic-Scan results across the examples and determine whether the failure is associated with the App cutover or the scanning infrastructure; done means the cause and ongoing impact are documented.

Written by the indexing model from the issue text.