Troubleshoot Salesforce CLI

Here’s a list of Salesforce CLI errors and how to fix them.

Check Our GitHub Repository for Issues and Discussions

Don’t see your problem in this section? Then check out the issues that our customers and open-source community enter in the top-level Salesforce CLI GitHub repository.
Use the Doctor to Troubleshoot Problems

Quickly gather Salesforce CLI configuration data and run diagnostic tests with the doctor command. The main use case of the command is to easily generate information files that you can attach to GitHub issues or provide to Salesforce Customer Support. You can also use the doctor command to troubleshoot Salesforce CLI problems by interpreting the output yourself.
Debug Errors When Deploying or Retrieving Source

When you run project deploy start or project retrieve start, Salesforce CLI creates a temporary directory with all the metadata files, and then deletes the directory upon successful completion of the command. If you run into errors when executing either command, retaining these files can be useful for debugging purposes.
Error: Bad CPU Type

You get the error Bad CPU type in executable when you try to install Salesforce CLI on macOS.
Where is Salesforce CLI Installed?

When troubleshooting installation problems, it’s often useful to know which directories Salesforce CLI is installed in.
Error: Command Failed with ENOENT

After recently installing Salesforce CLI, you get this error when you run a command such as project generate.
Error After Installing Salesforce CLI on PowerShell Using npm

After installing Salesforce CLI on Windows PowerShell using npm, you get a security policy error whenever you try to execute any CLI command. Installing with the Windows-specific installer works correctly.
Error Installing on Windows About the PATH Not Updated

While installing Salesforce CLI on Windows using the *.exe installer executable, you get the error PATH not updated, original length XX > 1024, where XX is a number greater than 1024.