Salesforce Metadata: notification delay after running a Retrieve/Deploy command on folder

[AndrewStopchenko-SO]

Summary

After Salesforce Metadata extension introduced (66.5.2 version?), there is a noticeable time delay between running the deploy/retrieve command on a component/project folder and the "Retrieving X Components" / "Deploying X Components" notification message that follows the command.

Steps To Reproduce:

1. Spin up the dreamhouse-lwc project with a fresh scratch org. Push sources to the org first time.
2. In Explorer, right-click on the force-app folder, select "SFDX: Retrieve This Source from Org" command.
3. If some changes got retrieved from the org and caused some local diffs to git main branch, reset all those local changes.
4. In Explorer, right-click on the force-app folder again, select the "SFDX: Deploy This Source to Org" command.

Expected result

On steps 2 and 4, once the context menu disappears (meaning, the command execution should have started), the notification message should appear immediately - as this was in 66.4.4 and earlier versions.

Actual result

Notice the time delay between the context menu disappearing, and the notification message being displayed.

I checked the times in both Windows 10 and the WSL. I got slightly lower delays on WSL (~2-3 seconds), but Windows 10 gives me ~3-5 seconds of delay.

Please find the Performance trace captured in Windows 10. It took ~4.7 seconds for notification to appear on deploying to org (Step 4):
VSCode_SalesforceExtensions_retrieveComponents_delay__Trace-20260415T130013.zip

Additional information

Salesforce Extension Version in VS Code: 66.5.4

Salesforce CLI Version: @salesforce/cli/2.130.9 win32-x64 node-v22.22.2

OS and version: Windows 10 (Windows_NT x64 10.0.19045)

VS Code version: 1.116.0

Most recent version of the extensions where this was working: 66.4.4

[svc-idee-bot]

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

[AndrewStopchenko-SO]

It looks like this might be addressed via the #7187 Pull Request.

[mshanemc]

yep, that's the idea! We're trying to provide a bit more transparency into what's going on (crawling your project vs. checking conflicts vs. the actual deploy) than what we had before (considering all that as "deploying").