-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recently the org display
command is intermittently taking quite a long time to complete
#2542
Comments
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. |
Hello @SCWells72 👋 None of the versions of Shared: Update to the latest version of Salesforce CLI (docs) and confirm that you're still seeing your issue. After updating, share the full output of |
I just updated to the latest-and-greatest. I've seen this for a few weeks so across multiple builds, so I doubt it's resolved by this most recent update. I'll post an update here if/when I see it occur again. New version info:
|
This issue has not received a response in 7 days. It will auto-close in 7 days unless a response is posted. |
I just chatted with @mshanemc about this and he asked me to log it here. In the past couple of weeks, I've seen the
org display
command (executed viasfdx force:org:display
by IC2) taking quite a long time to complete, e.g.:It doesn't happen consistently at all, but obviously when it does happen, it's quite annoying and unclear whether the CLI is actually going to complete, particularly since that particular command traditionally (and normally) only takes a few seconds to complete. Other commands seem fine, and it's not limited to a single org or set of orgs, though again, the same command against the same org may complete in 2-3 seconds on the next execution.
Let me know if there's any other info I can provide, though where this is an intermittent issue, it may be difficult to capture in-the-wild.
Here's the CLI version info:
The text was updated successfully, but these errors were encountered: