Azure / Azure/static-web-apps

Production slot deployment fails with "Failure during content distribution" for >2450 files (preview envs succeed)

Open
#1,735 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
346
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Hi team,

I'm running into a deployment issue that I wanted to report. Deploys to my production slot fail with "Failure during content distribution" once my artifact has around 2500+ files, but the same content deploys fine to preview environments.

Here's what I've observed:

- 2,439 files (296 MB) — deploys successfully to production slot
- 2,500 files (326 MB) — fails on production slot after ~5 minutes with "Failure during content distribution"
- 3,000+ files on a preview environment (same content, same SWA) — always succeeds

The artifact is well under the 500 MB Standard tier limit, so it's not a size issue. The upload phase completes fine. The failure happens during Azure's internal distribution step.

Setup:
- Azure SWA Standard tier, West Europe
- SWA CLI 2.0.8
- StaticSitesClient build 08e29138cd3dcda4ffda6d587aa580028110c1c7

The failing deployment ID is `c612cdea-5d64-47bf-a7c0-84ddbe0c9df2` if anyone can look it up on your end.

My use case is prerendering ~7,000 property listing pages for SEO. I've worked around it by capping at ~2,300 pages, but it means I can't prerender the full catalog.

A few questions:

1. Is there an undocumented file count limit for production slot deployments that preview slots don't have?
2. Why does the same content deploy fine to preview but fail on production?
3. Is there detailed logging available for that deployment ID that would show the actual failure reason? The CLI just says "Failure during content distribution" with no additional details.

Happy to provide more info if useful.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.