Azure devops release pipeline not loading

Question

Azure devops release pipeline not loading

roy 0

It just shows the spinner forever.

I need to release my build. Any help?

Gursimran Singh 160 Reputation points Microsoft External Staff Moderator

2026-07-16T12:54:34.3366667+00:00
Hi @roy ,

Could you please share the following details for further investigation?

Is the issue occurring for a specific Release Pipeline or for all Release Pipelines?

Does the issue persist in a different browser or an InPrivate/Incognito session?

Please share a screenshot of the page showing the continuous loading spinner.

Kindly collect and share any errors from the browser Developer Tools (F12 → Console and Network tabs).

You may share the requested details via private message if preferred.

1 answer

Your answer

Gursimran Singh 160 Reputation points Microsoft External Staff Moderator

2026-07-16T12:54:34.3366667+00:00

Hi @roy ,

Could you please share the following details for further investigation?

Is the issue occurring for a specific Release Pipeline or for all Release Pipelines?

Does the issue persist in a different browser or an InPrivate/Incognito session?

Please share a screenshot of the page showing the continuous loading spinner.

Kindly collect and share any errors from the browser Developer Tools (F12 → Console and Network tabs).

You may share the requested details via private message if preferred.

Answer 1

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

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.
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.
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.
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.
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.
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.