Hi @Edgar Aguilar
Thank you for posting your question in the Microsoft Q&A forum.
Based on my findings, there isn’t currently any official documentation or prior discussion that directly addresses this issue. The validation tool skips the Upload and Install steps when it cannot provision a sandbox environment. When sandbox provisioning fails or only partially succeeds, the validator completes the static checks but silently skips all environment‑dependent steps. Because no hard error is triggered, the run is reported as successful even though no upload or installation validation actually occurred.
The “Sandbox Resources are not available” message does not indicate any daily usage quota on your side, the HTTP 412 response indicates that the preconditions for creating a sandbox environment weren’t met. In practice, this usually happens when the shared sandbox infrastructure in a given region is temporarily saturated or unstable. When that occurs, new sandbox requests are blocked and retries will continue to fail until capacity is restored. This explains why the error can persist for hours or even the rest of the day, regardless of changes to the app or manifest.
Unfortunately, there is no client‑side way to reset or force the sandbox to become available. The only practical options are to wait for the regional sandbox pool to recover, often after some time or overnight. Once backend capacity is freed up, the validator will automatically resume full runs without any action required on your part.
I hope this information is helpful.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.