Azure devops release pipeline not loading

roy 0 Reputation points
2026-07-16T08:42:18.69+00:00

It just shows the spinner forever.

I need to release my build. Any help?

Azure DevOps

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Gursimran Singh 495 Reputation points Microsoft External Staff Moderator
    2026-07-17T13:16:58.5733333+00:00

    Hi @roy

    Thank you for the update.

    The information suggests that uBlock Origin may be blocking content required by the Azure DevOps Release Pipeline page. However, since this behavior was not observed previously, we cannot determine from the available information what specifically changed to trigger the issue.

    Could you please confirm whether the Release Pipeline loads successfully when uBlock Origin is disabled or when Azure DevOps is added to the extension allowlist?

    This will help determine whether the behavior is directly related to the browser extension or if additional investigation is required.

    Was this answer helpful?

    1 person found this answer helpful.

  2. AI answer

    2026-07-16T08:43:02.5733333+00:00

    If the Azure DevOps release pipeline page keeps spinning, check these common causes first:

    1. Verify the build pipeline completed at least once. If the build has never run successfully, the release can have no artifact to load. In Azure DevOps, run the build pipeline first and confirm it produced a pipeline artifact. Then go to Pipelines > Release and select Create release again.
    2. Check whether the release is actually waiting for approval. A release can appear stuck because the next stage is blocked on approval. Review the stage status and any configured approvals/checks.
    3. Check parallel job concurrency. Go to Project settings > Parallel jobs.
      • Select the relevant pool.
      • Choose View in-progress jobs.
      • If it shows Currently running X/X jobs, the release is queued and waits until another job finishes.
      • Queued jobs can also be reviewed under Project settings > Agent pools.
    4. If the release is waiting for an agent and never starts, check agent health and firewall access. Older artifact tasks such as PublishBuildArtifacts and DownloadBuildArtifacts can fail or hang in firewalled environments if agents cannot update or reach required blobstore domains. Common symptoms include SSL handshake errors, artifact download failures, agents going offline during update, or releases waiting for an agent that never arrives.
    5. If the release opens but deployment later hangs or fails with 503/5xx errors, check the target App Service. In the Azure portal:
      • Confirm the App Service is running.
      • Check App Service Plan capacity.
      • Scale up the App Service Plan if needed.
      • Review Kudu logs.
      • For production deployments, consider deployment slots instead of deploying directly to production.
    6. If the issue is with service connections, validate them. In Azure DevOps, go to Project settings > Service connections and verify the connection works.

    A practical end-to-end path is:

    • Run the build pipeline and confirm an artifact exists.
    • Create the release again.
    • If it still spins, check Parallel jobs and Agent pools.
    • If a stage does not advance, check approvals.
    • If deployment starts but hangs, inspect the target App Service and Kudu logs.
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.