SWA fails immediately after deployment with the swallowed An unknown exception has occurred.

Hi @Brandon Smith

Thank you for reaching us regarding the issue.

The error "An unknown exception has occurred" during Azure Static Web Apps deployment is documented as a known issue in the context of deployments.
Recommended Troubleshooting Steps:

• Retrieve deployment error messages: Review detailed logs in GitHub Actions (if using workflows) or run deployments with maximum verbosity/debug flags.
• Confirm folder configuration: Ensure app_location, output_location, and api_location (if applicable) in your workflow or deployment settings match your project structure.
• Check deployment status: Environments stuck in WaitingForDeployment indicate the process has not progressed past the initial upload phase.
• Use the Diagnose and solve feature in the Azure portal for guided troubleshooting.

For CLI-based deployments, enable debug logging and verify authentication, build outputs, and required configuration files (e.g., staticwebapp.config.json).

Reference:
https://learn.microsoft.com/en-us/azure/static-web-apps/troubleshooting
https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/troubleshoot?tabs=Browser

Kindly let us know if the above helps or you need further assistance on this issue.

Please "accept" if the information helped you. This will help us and others in the community as well.

Hi ,

Thanks for reaching out to Microsoft Q&A.

This is almost certainly a platform-side regression in azure Static Web Apps deployment service, not your CLI, region, or payload. Your evidence is strong: cross-region repro, cross-client (CLI + direct binary), minimal payload failure, and identical opaque exception indicates the failure is happening inside the StaticSites backend (deployment orchestrator or content ingestion layer) before logs are surfaced. The “WaitingForDeployment” state confirms the job is accepted but crashes during internal processing, and the swallowed exception aligns with the known issue (#1750) where the deploy client masks server-side faults. At this point, there is no reliable client-side workaround, version rollback, token reset, or payload simplification will not help. The only practical path is to raise a Microsoft support ticket with deployment IDs (you already have good samples) so engineering can trace backend logs; alternatively, wait for a service fix. If this is blocking, consider temporarily switching to GitHub Actions based deployment or using Azure Front Door + Storage static hosting until the SWA deployment pipeline stabilises.

Please 'Upvote'(Thumbs-up) and 'Accept' as answer if the reply was helpful. This will be benefitting other community members who face the same issue.