Slow and flaky

[AdamC-ST]

Summary

What has happened to this plugin recently?
It has made VS Code INCREDIBLY slow (5-10 seconds to paste text!) and the Deploy Source flow has completely changed, and for the worse.

Steps To Reproduce:

1. Open an Apex class
2. Right-click on it and select SFDX: Deploy This Source to Org

Expected result

1. Popup message stating code is being deployed, and remains until deployment complete
2. In Output tab, it switches to the appropriate output (was Salesforce CLI but now seems to be Salesforce Metadata) automatically and displays: Start/end time of deployment, List of any conflicted files (which may or may not be part of the deployment), success status when complete.

Actual result

1. Popup message takes a long time to appear (can be > 1 minute, which makes me question if I've even started a deployment), and doesn't remain visible until deployment complete
2. Output tab doesn't switch automatically to the correct output (which now seems to be Salesforce Metadata
3. When switched manually and presuming the deployment works, the Start/End time of deployment isn't shown, nor are the conflicted files.
4. Today, it has gotten even worse. On deployment, the only feedback in Output is:

Conflicts: Found 1 file in conflict
Starting metadata deployment...
Cannot read properties of null (reading 'startsWith')

The only indication it has succeeded is the Cannot read properties of null (reading 'startsWith') message (which I've checked a few times with SFDX: Diff Source Against Org)

Diff is behaviour has changed too.
Now, if the local and Org code is the same, the diff isn't opened showing that. Sometimes a message flashes up to say there are no differences but it is inconsistent.

Additional information

Feel free to attach a screenshot.

Salesforce Extension Version in VS Code:
salesforce.salesforcedx-vscode: Version 66.8.0

Salesforce CLI Version:
@salesforce/cli/2.131.7 win32-x64 node-v22.20.0

OS and version:
WIndows 11 23H2 Build 22631.6199

VS Code version:
Version: 1.117.0 (user setup)
Commit: 10c8e557c8b9f9ed0a87f61f1c9a44bde731c409
Date: 2026-04-21T16:12:14-07:00
Electron: 39.8.7
ElectronBuildId: 13841579
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.22631

Most recent version of the extensions where this was working:
It's been poor for a month or so now. It improved a tiny bit last week, but now it's even worse

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

[mshanemc]

I've not been able to recreate this bug, but I'm sure it's real because of several similar reports. Can you run the SFDX Generate Project Info and provide the results?

I think there's something in source tracking that causes this.

[AdamC-ST]

Hi Shane, Project info, as requested, attached. Even this took approx 30s before the popup said it was being generated. I hope you find the source of this issue. Everything not just deployments, is slow - it really is slowing me down and is quite frustrating. Regards, Adam

…

On Thu, 30 Apr 2026 at 16:22, Shane McLaughlin ***@***.***> wrote: *mshanemc* left a comment (forcedotcom/salesforcedx-vscode#7278) <#7278 (comment)> I've not been able to recreate this bug, but I'm sure it's real because of several similar reports. Can you run the SFDX Generate Project Info and provide the results? I think there's something in source tracking that causes this. — Reply to this email directly, view it on GitHub <#7278 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGGUDSJW2XWIPCDEXOJD2OD4YNVR7AVCNFSM6AAAAACYMLKHH6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGNJTG42TIOJVGA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[mshanemc]

I don't think attachments on email end up on github.

[AdamC-ST]

project-info.md
Here you go!

[AdamC-ST]

Shane, File added directly to Git. I think there's something in source tracking that causes this. That may explain the slow deployment process, but not the generally slow responses in VS Code. Also, while the project is constantly changing, it hasn't changed substantially in size in the last year or so, and these issues weren't happening then - it is quite a recent problem. Thanks for investigating this Regards Adam

…

On Thu, 30 Apr 2026 at 17:10, Shane McLaughlin ***@***.***> wrote: *mshanemc* left a comment (forcedotcom/salesforcedx-vscode#7278) <#7278 (comment)> I don't think attachments on email end up on github. — Reply to this email directly, view it on GitHub <#7278 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BGGUDSOI2LCRTHQ3HWFOLP34YN3INAVCNFSM6AAAAACYMLKHH6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGNJUGEYTQMBZGU> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[AndrewStopchenko-SO]

I'd like to add about the "slow VSCode response".

In my mid-size SF project (working with a Sandbox org; source tracking is enabled), I see that after saving any file inside a Salesforce project - literally test1.txt file - there is a large delay before the file gets actually saved, and also the typed characters appear in the file body with a noticeable delay.

It feels like there's some background process (a file watcher?) that kicks off some heavy-lifting operations once the file gets saved, using resources so actively that it even delays any text editing operations.

For example, if I save the empty text1.txt file and immediately start typing "1" symbols repeatedly, those "11111111..." characters will only appear in the text1.txt file after some 0.5-2 seconds.

• This might start happening after repeating "edit-save" 2-3 times, but the "delayed typed characteds" becomes extremely annoying when trying to edit the code.
• I tried same editing exercises in a non-Salesforce project folder (where Salesforce extensions do not activate), no delay detected there.
• I was able to reproduce this to some extent (the delay is much lighter - probably because the project has less components in it) in a dreamhouse-lwc Salesforce project connected to the scratch org, after running the sf project tracking delete command.

Could this be related to the automatic detection of conflicts/changes between project and org for the "source tracking details" toolbar item?

---

project-info.md result from the affected project

# Project Info

Generated: 2026-05-05T19:14:06.819Z

## Metadata

sourceApiVersion: 64.0
packageDirectories: 1
namespace: 

### Types

| Type | Components | Files | Size (KB) |
| --- | --- | --- | --- |
| ApexClass | 190 | 570 | 2362 |
| ApexPage | 10 | 30 | 66 |
| ApexTrigger | 17 | 51 | 66 |
| ApprovalProcess | 6 | 6 | 22 |
| AssignmentRules | 2 | 2 | 32 |
| AuraDefinitionBundle | 11 | 73 | 76 |
| AuthProvider | 14 | 14 | 8 |
| AutoResponseRules | 2 | 2 | 4 |
| ContentAsset | 10 | 30 | 3754 |
| CustomLabels | 1 | 1 | 14 |
| CustomMetadata | 141 | 141 | 100 |
| CustomNotificationType | 5 | 5 | 2 |
| CustomObject | 118 | 5501 | 5788 |
| CustomPermission | 27 | 27 | 8 |
| CustomTab | 9 | 9 | 2 |
| DuplicateRule | 5 | 5 | 8 |
| EscalationRules | 1 | 1 | 3 |
| FlexiPage | 725 | 725 | 17836 |
| Flow | 351 | 351 | 8674 |
| FlowDefinition | 351 | 351 | 56 |
| FlowTest | 2 | 2 | 18 |
| GlobalValueSet | 12 | 12 | 40 |
| Group | 67 | 67 | 12 |
| HomePageLayout | 1 | 1 | 1 |
| Layout | 352 | 352 | 2027 |
| LeadConvertSettings | 1 | 1 | 32 |
| LightningComponentBundle | 14 | 59 | 175 |
| MatchingRules | 6 | 6 | 2 |
| MutingPermissionSet | 1 | 1 | 1 |
| NamedCredential | 12 | 12 | 7 |
| PermissionSet | 263 | 263 | 5113 |
| PermissionSetGroup | 62 | 62 | 48 |
| PlatformEventChannelMember | 3 | 3 | 1 |
| Queue | 31 | 31 | 14 |
| QuickAction | 74 | 74 | 87 |
| RemoteSiteSetting | 12 | 12 | 4 |
| ReportType | 170 | 170 | 8086 |
| Role | 88 | 88 | 38 |
| SharingRules | 4 | 4 | 0 |
| StandardValueSet | 8 | 8 | 36 |
| StaticResource | 3 | 9 | 7246 |
| Workflow | 14 | 14 | 121 |

## Org

| Key | Value |
| --- | --- |
| Org type | sandbox |
| Source tracking | true |
| SourceMember count | 1908 |

## Settings

| Setting | Value |
| --- | --- |
| salesforcedx-vscode-metadata.showSuccessNotification | true |
| salesforcedx-vscode-metadata.sourceTracking.pollingIntervalSeconds | 60 |
| salesforcedx-vscode-core.push-or-deploy-on-save.enabled | false |
| salesforcedx-vscode-core.push-or-deploy-on-save.ignoreConflictsOnPush | false |
| salesforcedx-vscode-core.detectConflictsForDeployAndRetrieve | false |
| salesforcedx-vscode-core.clearOutputTab | false |
| salesforcedx-vscode-core.show-cli-success-msg | true |
| salesforcedx-vscode-core.telemetry.enabled | false |
| salesforcedx-vscode-core.enable-sobject-refresh-on-startup | false |
| salesforcedx-vscode-core.telemetry-tag |  |
| salesforcedx-vscode-salesforcedx.enableLocalTraces | false |
| salesforcedx-vscode-salesforcedx.enableConsoleTraces | false |
| salesforcedx-vscode-salesforcedx.enableFileTraces | false |
| salesforcedx-vscode-apex.java.home | C:\\Java\\zulu-21 |

## Environment

| Key | Value |
| --- | --- |
| Salesforce CLI | @salesforce/cli/2.132.14 win32-x64 node-v22.22.2 |
| Java | java 11.0.12 2021-07-20 LTS |
| VS Code | 1.118.1 |
| Node | v22.22.1 |
| OS | Windows_NT 10.0.19045 |

## Extensions (Salesforce)

| Extension | Version |
| --- | --- |
| salesforce.apex-language-server-extension | 0.4.0 |
| salesforce.salesforcedx-vscode | 66.9.0 |
| salesforce.salesforcedx-vscode-apex | 66.9.0 |
| salesforce.salesforcedx-vscode-apex-log | 66.9.0 |
| salesforce.salesforcedx-vscode-apex-replay-debugger | 66.9.0 |
| salesforce.salesforcedx-vscode-apex-testing | 66.9.0 |
| salesforce.salesforcedx-vscode-core | 66.9.0 |
| salesforce.salesforcedx-vscode-metadata | 66.9.0 |
| salesforce.salesforcedx-vscode-org | 66.9.0 |
| salesforce.salesforcedx-vscode-org-browser | 66.9.0 |
| salesforce.salesforcedx-vscode-services | 66.9.0 |
| salesforce.salesforcedx-vscode-soql | 66.9.0 |
| salesforce.salesforcedx-vscode-visualforce | 66.9.0 |

[daphne-sfdc]

👋 @AdamC-ST and @AndrewStopchenko-SO - We'd like to do some tracking of which step of the deployment is acting slowly. Can you please help us collect info by doing the following?

1. Go to your VSCode User settings.json and add "salesforcedx-vscode-salesforcedx.enableFileTraces": true.
2. Reload the VSCode window.
3. Do a deploy and wait for it to complete.
4. Files are captured to $HOME/.sf/vscode-spans. Zip up that folder and email it to us at svc_idee_bot@salesforce.com.

[AndrewStopchenko-SO]

Zip up that folder and email it to us at svc_idee_bot@salesforce.com.

@daphne-sfdc Hi Daphne, have just sent out the zip archive to the email above.
I edited an apex class by adding a new empty line and deploying via the editor's context menu "SFDX: Deploy This Source to Org" command.

Also wanted to mention that during these actions, the source tracking in the SF Project is out of sync (1 conflict, 287 remote changes, 352 local changes) - from what I can tell, the higher these numbers, the higher the chance to experience that "laggy VS Code" behavior.

[daphne-sfdc]

Hi @AndrewStopchenko-SO, We took your traces and put them into Grafana for analysis. We found that the slowdown seems to happen either in the SDR library or in the org on the server side. Can we get a bit more data from you? It would be helpful if you could deploy the same file via CLI that you did for the extensions and see how long that takes, for comparison. Thanks!

[AdamC-ST]

@daphne-sfdc
Hi Daphne,
I tried the enable file traces but no file was created in .sf
But, I did notice, in \.sf\orgs\00DRu00000QeSeXMAV\localSourceTracking\objects\, there are 258 folders (named like 00, 3a etc), each of which has 40-60 files with GUID like names and binary content.

Also, in VS Code status bar, it shows 'differences' - 501 remote changes and 193 local changes.
I don't know why it would show this - this is a Scratch Org, to which I deployed our Package and then I've been working on, but I've only changed a few files and all of those have been deployed. There shouldn't really be any differences. No one else is using this Scratch Org.

By contrast, in our Dev org where we do builds, and a few of us have been working (so some differences may be expected), and which has the same package, same metadata, the \localSourceTracking\ folder doesn't even exist. No differences are shown in the Status bar. This instance of VS code works normally.

Hope this is useful!