You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
From what I've been able to tell when trying to add the "Team" it breaks the team out to its individual users, when I hit the share option, it's almost like as it loops through the users to add, it is timing out or maybe hitting a user that it doesn't know how to handle. I can see that it doesn't remove suspended and deactivated users from the team; maybe that's it?
I'm not sure, but I figured sending that extra information might help.
Hi, Michael, we did some initial investigation and our team thought it could be a few things:
1. As a fix for another incident, the team introduced a rate limit last week on sharing a project to 50 shares per workspace, per hour. You could be hitting the limit if the people in the workspace are sharing a lot at the moment, but the team is not convinced this is what's causing sharing to fail.
2. The team also tried inviting 4 users on a test instance and found it to be sluggish so it's possible the request timed out.
3. The team also noticed that if any one of the users added either directly or by email fails Atlas shows a failure toast/flag even though a bunch of others may be successfully added as followers.
I don't know if this information will help and I don't have any other updates here yet but I will keep you informed as I look into this more.