Skip to content

Deployments failing with "Failure during content distribution" — zero correlation with repo content, tested extensively #1803

Description

@Shivahotelsnet

The blocker: deployments are currently broken, unrelated to any of this.
Since yesterday's last successful deploy, every single push to main has failed at Azure's "content distribution" step — tested exhaustively:

Full Telegram feature added → failed
Symlinks removed (unrelated pre-existing issue) → failed
Everything fully reverted to the last known-good state → failed
A single-line trivial comment change → failed
Pushed from a second computer → failed
Waited 15 min between attempts → failed
Regenerated the deployment token → failed
Service Health shows no incidents

This rules out repo content, dependencies, size, symlinks, timing, and the deployment token as causes. It's a stuck/broken state on Azure's side for this specific resource.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions