retrieve/deploy command takes too long to finish.

[Bluewine]

Expected result

The following actions:

• sf project retrieve/deploy start --manifest <manifest.xml> --ignore-conflicts -o <target-org-alias>
• From VS Code, right click on a component (Apex, LWC, Aura, anything) and Retrieve/Deploy/Diff

Should take at most 1 (or 2, intolerable) mins to finish.

Actual result

The following actions:

• sf project retrieve/deploy start --manifest <manifest.xml> --ignore-conflicts -o <target-org-alias>
• From VS Code, right click on a component (Apex, LWC, Aura, anything) and Retrieve/Deploy/Diff

Take 5 - 10 mins to conclude.

Additional information

N/A

System Information

CLI:
@salesforce/cli/2.71.6 win32-x64 node-v22.12.0

Plugin Version:
@oclif/plugin-autocomplete 3.2.14 (core)
@oclif/plugin-commands 4.1.14 (core)
@oclif/plugin-help 6.2.19 (core)
@oclif/plugin-not-found 3.2.31 (core)
@oclif/plugin-plugins 5.4.22 (core)
@oclif/plugin-search 1.2.17 (core)
@oclif/plugin-update 4.6.18 (core)
@oclif/plugin-version 2.2.18 (core)
@oclif/plugin-warn-if-update-available 3.1.28 (core)
@oclif/plugin-which 3.2.21 (core)
@salesforce/cli 2.71.6 (core)
apex 3.6.8 (core)
api 1.3.2 (core)
auth 3.6.82 (core)
data 3.13.5 (core)
deploy-retrieve 3.16.0 (core)
info 3.4.29 (core)
limits 3.3.43 (core)
marketplace 1.3.7 (core)
org 5.2.11 (core)
packaging 2.9.7 (core)
schema 3.3.45 (core)
settings 2.4.9 (core)
sobject 1.4.46 (core)
telemetry 3.6.27 (core)
templates 56.3.34 (core)
trust 3.7.51 (core)
user 3.6.5 (core)

SF ENV. VARS.
SF_AUTOUPDATE_DISABLE,true
SF_BINPATH,C:\Users\HeanG\AppData\Local\sf\client\bin\sf
SF_DISABLE_AUTOUPDATE,true
SF_UPDATE_INSTRUCTIONS,Use "npm update --global @salesforce/cli" to update npm-based installations.

Windows: true
Shell: powershell
Channel: stable

---

Diagnostics

✅ pass - salesforcedx plugin isn’t installed
✅ pass - you don't have any linked plugins
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.yarnpkg.com
✅ pass - [@salesforce/plugin-trust] can ping: https://registry.npmjs.org/
✅ pass - using latest or latest-rc CLI version
✅ pass - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches apiVersion
✅ pass - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches default target org max apiVersion
✅ pass - can access: https://test.salesforce.com
✅ pass - can access: https://appexchange.salesforce.com/services/data
✅ pass - [@salesforce/plugin-auth] CLI supports v2 crypto
✅ pass - [@salesforce/plugin-auth] CLI using stable v1 crypto
✅ pass - can access: https://developer.salesforce.com/media/salesforce-cli/sf/channels/stable/sf-win32-x64-buildmanifest

[iowillhoit]

Hello @BlueWin, this is not enough information for us to investigate.

• How much metadata are you deploying?
• What stage of the deploy/retrieve output is taking the longest?
• Did this used to be faster and it suddenly slowed down?
• Can you provide the output with the --dev-debug flag?

The CLI's involvement with deploys and retrieves is pretty minimal. We prepare files and send them to the server. It is unlikely that it is actually an issue with the CLI, but I cannot tell from the lack of details.

[ethanzhoujie]

+1.

I use retrieve

❯ sf project retrieve start --package-name 'SmartQuote' --target-org [email protected]

────────────── Retrieving Metadata ──────────────

Retrieving v62.0 metadata from [email protected] using the v63.0 SOAP API

✔ Preparing retrieve request 16ms
✔ Sending request to org 191ms
✔ Waiting for the org to respond 16m 20.49s
✔ Done 0ms

Status: Succeeded
Elapsed Time: 16m 26.67s

Four files, not big.

[AnonyEastRainbow]

+1

I waited for 28 minutes without successfully pulling, only pulling one object.I have been encountering this problem frequently recently.I have already used the latest CLI version.

[iowillhoit]

Spring 25 is currently rolling out to customers. @ethanzhoujie, it looks like you are on Spring 25 because of the 63.0 SOAP API message.

In the past we have seen some slowness in deploys/retrieves as a new major version has rolled out. There is a Known Issue that appears to be related.

Unfortunately, there is nothing the CLI team can do to resolve this.