Module Connection keeps flipping between alias and username for CLI connections

[Michael Richmond]

Periodically the connection for the my SFDX project keeps flipping back and forth between the alias and username. Not a huge deal, but it prompts me to update the connection and then I have to restart the application for re-indexing. Fortunately it picks up the OST so this process is relatively quick but it’s still annoying.

When doing a sfdx force:org:list the connection still has its alias listed.

Any ideas on what would be causing this?

‌

‌

So far I have not seen any pattern to reproduce this.

Looking in the idea.log I do see this.

2020-06-18 20:34:43,250 [ 366141]   INFO - .IlluminatedCloudExceptionUtil - Pushed 0/1 components to athp in 3 s 49 ms with status 1. 
2020-06-18 20:34:43,262 [ 366153]   INFO - .IlluminatedCloudExceptionUtil - Push details:
{
  "successes": [],
  "failures": [
    "NoOrgFound - No org configuration found for name --json"
  ],
  "numSuccesses": 0,
  "numFailures": 1
} 

‌

[Scott Wells]

Michael, this was an issue in the Salesforce CLI a few weeks back. Can you please make sure that you're on the very latest build of the CLI using sfdx update? I'm updating to today's build right now (though this should have been fixed about 2-3 weeks ago) and it's showing a version of 7.63.0.

Let me know if this problem isn't resolved by updating.

[Scott Wells]

More specifically, this is the output of sfdx plugins on the latest:

salesforcedx 48.19.0
├─ @salesforce/sfdx-plugin-lwc-test 0.1.5
├─ custom-metadata 1.0.1
├─ salesforcedx-templates 48.18.0
└─ salesforce-alm 48.20.0

[Michael Richmond]

Thanks Scott.

I’ve installed the CLI using npm and was having issues updating to the latest version this week. Looks like whatever was preventing the upgrade has been resolved so I am running 7.63.0 and 48.19.0 for the salesforcedx plugin.

I’ll see how it goes tomorrow and resolve the issue if I don’t see any issues.

[Scott Wells]

Hi, Michael. Good to know. Please let me know if the issue doesn't go away so that we can gather some logs that I can share with Salesforce (with your permission, of course).

[Michael Richmond]

Hi Scott. I haven’t seen this issue today, so I’m going to mark as resolved. If it happens again I’ll open another issue.

[Scott Wells]

Sounds great! Thanks for the update.