Browser and desktop app not showing a new team that I am a member of

[Lisa Stebbins]

I create a new private team today and added some users to it. They said that it doesn't show up in the list of teams in the browser (Edge or Chrome) nor in the desktop app. I tested it with a test user and had the same experience. I deleted the users and re-added them as members. That didn't work. I deleted them and generated a code and had them use it. It appeared briefly but when I refreshed the browser, it disappeared again. It is not hidden.

Anyone experienced this? Anyone have any idea what is going on?

[#2]

How did you create the Team? If you did anywhere other than Teams, there is usually a pretty long lag, before everything gets setup properly.

[#3]

@Chris Webb 

I created it in TEAMS using the Create or Join link, etc. I've never had a lag before or since with other new TEAMS. It seems to be related to this one....maybe...? Is there a setting that can cause it to not display for its members? This TEAM has several guests; could that impact something somehow?

Interestingly enough, the other owners are able to access it; I am double checking with other members. Could there be an issue/diff between being an owner and member for some reason? I am checking with the other members to see if they have had any problems. I am also checking with other TEAMS owners (for TEAMS I've created since creating the one referenced here) to see if they have had any issues with their members' displays.

I tested by promoted my test user from member to owner and the TEAM immediately popped up in my user's list in its TEAMS app! When I demoted the user back to member, the TEAM remains in the list.

[#4 · Accepted solution]

I did not find any other instances or assistance on this from others who have experienced it. So, I deleted the TEAMS etc. and created a new one using the same method as I did for the first one. It seems to be working fine so the problem must have been caused by an incomplete creation process on the first one of some kind. The only casualty was the URL which followed our naming convention. I couldn't delete the site permanently since it was TEAMS (had to wait the 30 day period) so I had to 'fudge' the naming convention a little to be able to create a new one.