nuget.exe - Pushing took too long - 503 error during azure devops artifact upload

(2) Share

Report

Posted on by EK-26061005-0

441

I'm trying to upload the necessary DevALM nuget packages for creating the build pipeline in our d365fo azure devops repository. I have managed to upload both the Application1-2 files and CompilerPackage via nuget.exe but the ApplicationSuite and Platform.DevALM files give the following error:

nuget.exe push -Source Contoso -ApiKey az -Timeout 3601 Microsoft.Dynamics.AX.ApplicationSuite.DevALM.BuildXpp.nupkg
Pushing Microsoft.Dynamics.AX.ApplicationSuite.DevALM.BuildXpp.nupkg to 'https://pkgs.dev.azure.com/Contoso/_packaging/a0171fac-7daf-4b75-b2c5-8356dd5c71ac/nuget/v2/'...
  PUT https://pkgs.dev.azure.com/Contoso/_packaging/a0171fac-7daf-4b75-b2c5-8356dd5c71ac/nuget/v2/
  ServiceUnavailable https://pkgs.dev.azure.com/Contoso/_packaging/a0171fac-7daf-4b75-b2c5-8356dd5c71ac/nuget/v2/ 137005ms
  PUT https://pkgs.dev.azure.com/Contoso/_packaging/a0171fac-7daf-4b75-b2c5-8356dd5c71ac/nuget/v2/
  ServiceUnavailable https://pkgs.dev.azure.com/Contoso/_packaging/a0171fac-7daf-4b75-b2c5-8356dd5c71ac/nuget/v2/ 137989ms
  PUT https://pkgs.dev.azure.com/Contoso/_packaging/a0171fac-7daf-4b75-b2c5-8356dd5c71ac/nuget/v2/
  ServiceUnavailable https://pkgs.dev.azure.com/Contoso/_packaging/a0171fac-7daf-4b75-b2c5-8356dd5c71ac/nuget/v2/ 141430ms
Response status code does not indicate success: 503 (Service Unavailable).

What's weird is: Application1 took 278 seconds to upload but the remaining packages throw the error after 135 seconds.

Categories:

Dynamics 365 Finance

I have the same question (1)

All responses (4)

Answers (1)

Suggested answer

Saif Ali Sabri 2,351 Super User 2025 Season 2 on at

Like (0)

Report
This is a timeout issue likely caused by large package size or network latency. Azure DevOps may throttle or drop long uploads, especially through the legacy v2 endpoint.
Recommended Solutions:

Use the v3 endpoint (more reliable for large packages):
Update the source URL in your command:

bash CopyEdit
nuget.exe push -Source https://pkgs.dev.azure.com/Contoso/_packaging/YourFeedName/nuget/v3/index.json -ApiKey az -Timeout 3600 YourPackage.nupkg

Split large packages (if feasible):
Reduce package size if it's unusually large (e.g. >250MB).

Use dotnet nuget push instead (supports retries and better performance):

bash CopyEdit
dotnet nuget push YourPackage.nupkg --source "Contoso" --api-key az --timeout 3600

Retry during non-peak hours:
Azure DevOps feeds can be throttled under load.

Let me know your package size or if switching to v3 solves it.

Was this reply helpful? Yes No
EK-26061005-0 441 on at

Like (1)

Report

Hello @Saif Ali Sabri

I have already added the source with v3 endpoint but the PUT request uses v2 endpoint regardless. Using dotnet nuget did not make any difference either. Since the artifacts are default packages from the shared asset library and are used by build-pipeline, i don't think i can reduce the size of these packages.

Was this reply helpful? Yes No
Suggested answer

Saif Ali Sabri 2,351 Super User 2025 Season 2 on at

Like (0)

Report
Thanks for the clarification. Since:

You're already using the v3 endpoint, but nuget.exe still routes the upload to v2

dotnet nuget push doesn't help either

The packages are default, large D365 packages, and cannot be reduced

The issue is related to timeout (503 after ~135 seconds)

Recommended Workarounds:
✅ 1. Switch to Azure CLI (az artifacts) for pushing
It handles large uploads better than nuget.exe.
bash
CopyEdit
az artifacts universal publish \
--organization https://dev.azure.com/Contoso \
--feed YourFeedName \
--name Microsoft.Dynamics.AX.ApplicationSuite.DevALM.BuildXpp \
--version 1.0.0 \
--description "ApplicationSuite DevALM package" \
--path ./
❗You may need to wrap the .nupkg inside a directory, as Universal Packages work differently. This avoids NuGet-specific upload issues.
✅ 2. Use a self-hosted agent with higher upload speed
Hosted agents might experience throttling or latency. A self-hosted agent on Azure VM or local network can maintain stable upload throughput.
✅ 3. Manually upload via DevOps portal as temporary measure
Go to Azure DevOps → Artifacts → Upload Package, and upload the .nupkg manually to unblock yourself temporarily.

If this is a blocker in an automated pipeline, I recommend switching to Universal Packages or using Azure Artifacts REST API directly to bypass NuGet push limitations.
Let me know if you want the REST API method as well.

Was this reply helpful? Yes No
Verified answer

EK-26061005-0 441 on at

Like (1)

Report

The issue was resolved after switching to the admin account and using a connection with better upload speed (around 50Mbit/s)

Was this reply helpful? Yes No

Join the conversation

Community site session details

nuget.exe - Pushing took too long - 503 error during azure devops artifact upload

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates

Community site session details

nuget.exe - Pushing took too long - 503 error during azure devops artifact upload

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

Featured topics

Product updates