You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently ran into an issue with the Salesforce CLI when executing:
sf plugins discover
I received this error:
Error (ERR_NON_2XX_3XX_RESPONSE): Response code 429 (Too Many Requests)
I am not running any extra scripts or CI jobs. The command was run manually from my home network. I even downgraded to the earlier CLI version and tried disconnecting from my VPN, but the error persists.
Steps To Reproduce
run sf plugins discover
Expected result
get the available plugins
Actual result
Error (ERR_NON_2XX_3XX_RESPONSE): Response code 429 (Too Many Requests)
Summary
I recently ran into an issue with the Salesforce CLI when executing:
I received this error:
I am not running any extra scripts or CI jobs. The command was run manually from my home network. I even downgraded to the earlier CLI version and tried disconnecting from my VPN, but the error persists.
Steps To Reproduce
Expected result
get the available plugins
Actual result
Error (ERR_NON_2XX_3XX_RESPONSE): Response code 429 (Too Many Requests)
System Information
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
❌ warn - [@salesforce/plugin-deploy-retrieve] sourceApiVersion matches apiVersion
✅ pass - can access: https://test.salesforce.com
✅ pass - can access: https://appexchange.salesforce.com/services/data
✅ pass - can access: https://developer.salesforce.com/media/salesforce-cli/sf/channels/stable/sf-win32-x64-buildmanifest
❌ fail - [@salesforce/plugin-auth] CLI supports v2 crypto
✅ pass - [@salesforce/plugin-auth] CLI using stable v1 crypto
The text was updated successfully, but these errors were encountered: