Static Web App deployment consistently fails with 'Failure during content distribution' — build succeeds, only the publish step fails

SYMPTOM

Every attempt to deploy new content to this Static Web App fails at the same step, with the same

generic error, no matter what is being deployed:

Deployment Failure Reason: Failure during content distribution.

Error: The process '/usr/bin/bash' failed with exit code 1

The failure happens ~16-17 seconds after the build artifact is uploaded and polling begins — every

single time, almost to the second. The build/upload itself always completes successfully; the

failure is entirely on the publish/distribution side.

WHAT WE HAVE ALREADY RULED OUT

1. Our code/build — the build step (Oryx, npm install, zipping app + API artifacts, upload) succeeds on every attempt with no errors. The failure only occurs AFTER a successful upload, during Azure's own content-distribution step.
2. Payload size — total deployed content is ~8 MB, well under any documented Static Web Apps limit.
3. Deployment credential — we regenerated the deployment token via "Manage deployment token" in the Portal and updated the CI/CD pipeline's secret to match. The very next deployment attempt failed with the IDENTICAL error at the IDENTICAL step. A stale/invalid credential would be expected to fail differently (an authorization error), not identically — this rules out the token as the cause.
4. A broader Azure or regional outage — a DIFFERENT Static Web App in the SAME subscription (jcq-portal, resource group jcq-dashboards) deployed successfully via the same CI/CD mechanism DURING the window these failures were occurring. If this were a platform-wide or regional issue, that deployment would have failed too.

This points to something specific to this one resource's state in the content-distribution backend,

which we have no visibility into from the CI/CD pipeline logs or from az CLI queries against the

resource (provisioningState returns null; no errors, warnings, or unusual state shown on the resource

itself).

CURRENT IMPACT

The site is NOT down — it continues serving its last successfully published build (confirmed via

HTTP 302 responses, auth gate functioning normally) — but no new content can be published to it.

EVIDENCE: FAILED DEPLOYMENT ATTEMPTS

Deployment method: Azure DevOps pipeline (organization: jcqservices, project: dashboards, pipeline:

dashboards-deploy, pipeline ID 2), using the Azure Static Web Apps deploy task / StaticSitesClient.

Each attempt logs its own StaticSitesClient DeploymentId — the specific identifier your team can use

to pull internal content-distribution logs for that exact attempt:

Run ID Queued (UTC) DeploymentId Result Notes

4505 2026-08-11T21:51:00Z 60b8df14-34db-4d5f-b88f-19afb4e3c948 Failed First failure

4506 2026-08-11T21:55:09Z 82c8fd4b-5eca-40b4-ab7a-a4203046c213 Failed Retry

4507 2026-08-11T21:59:29Z 7d8eee9e-3e06-42e6-99a7-554b68322792 Failed Retry

4511 2026-08-11T22:09:15Z ba88e24b-f9f1-4e75-82dd-56b404c4605b Failed Retry

4512 2026-08-11T22:10:56Z 203c318d-a615-4dc1-954f-215bac49fdc8 Failed Retry

4517 2026-08-11T23:09:15Z 927d0524-719f-4321-bf3e-03c8fd442427 Failed Retry

4520 2026-08-12T00:57:45Z 1477b0fe-ca24-4b2a-b9d8-93533b0792c4 Failed Retry

4521 2026-08-12T01:03:56Z 45184739-0aaf-4ebc-92a6-b7fe8dcd29f9 Failed First attempt AFTER

                                                                              regenerating the

                                                                              deployment token —

                                                                              identical failure
```  4539     2026-08-12T08:45:03Z  e7cd47a3-80da-4f6e-87a5-200d8a244428    Failed   Retry, +10 hrs later

  4540     2026-08-12T12:59:23Z  937b997e-887e-441b-8ab3-9929438840bb    Failed   Retry, verbose/debug

```dockerfile
                                                                              logging enabled —

                                                                              same failure, no

                                                                              additional detail

                                                                              surfaced beyond the

                                                                              DeploymentId itself
```All ten attempts, spanning ~15 hours, produced byte-identical error text ("Failure during content

distribution.") and near-identical timing (~16.7-16.9 seconds from "Status: InProgress" to

"Status: Failed"), including with the deployment token freshly regenerated and with verbose logging

on. Please use the DeploymentIds above to look up why content distribution is rejecting every one of

these attempts for this resource specifically.

WHAT WE NEED

Please investigate the content-distribution backend state for this specific Static Web App resource

and clear whatever stuck/corrupted state is causing every deployment to fail at this step. Happy to

provide additional correlation IDs, request IDs, or timestamps if you can point us to where to find

them in the deployment response — the CI/CD task output does not surface one.

Hello @Sameer Tyagi

Please feel free to reach out to us in case of any further queries.