I'm getting an error when trying to invite a new u...
# ask-communitya
Adam Roderick
03/25/2020, 2:10 PMI'm getting an error when trying to invite a new user to our team in Prefect Cloud. Where should I go from here?
n
nicholas
03/25/2020, 2:13 PM
Hi @Adam Roderick do you know which plan you're on? It's possible that you're at your user limit (which is counted as current users + outstanding invitations)
a
Adam Roderick
03/25/2020, 2:15 PMIt says custom license when I look at the Billing tab. We are currently at 3 users
Adam Roderick
03/25/2020, 2:15 PMTeam name is "Datateer"
c
Chris White
03/25/2020, 2:16 PM
I just checked your license — you have no license-related limits you should be hitting
Chris White
03/25/2020, 2:17 PM
You do have an outstanding invitation though; can you check your “Invitations” tab and see if your invite shows up there?
a
Adam Roderick
03/25/2020, 2:18 PM🙄 sorry, I just saw the outstanding invitation. That's obviously where the error is coming from
c
Chris White
03/25/2020, 2:18 PM
No worries at all, the error message here is not very informative so I understand the confusion — we’ll work on updating that!
a
Adam Roderick
03/25/2020, 2:35 PMOriginal problem is solved. Here is some information for future reference:
Adam Roderick
03/25/2020, 2:35 PMThe developer on the machine that was failing had not activated their Cloud account
Adam Roderick
03/25/2020, 2:36 PMHe activated, but still had the same outcome from
flow.deployc
Chris White
03/25/2020, 2:36 PM
does he have docker running?
a
Adam Roderick
03/25/2020, 2:36 PMThen he went through the config process, generating a USER token and running
prefect authAdam Roderick
03/25/2020, 2:36 PMAfter that problem went away
c
Chris White
03/25/2020, 2:36 PM
oh wild
a
Adam Roderick
03/25/2020, 2:36 PM@Chris White yes, docker was running from the beginning
Adam Roderick
03/25/2020, 2:37 PMSo definitely user error, but I wanted to provide the context in case you want to capture this error in the future
c
Chris White
03/25/2020, 2:37 PM
Yea for sure I appreciate it; sorry I wasn’t of more help here --> I’m still not entirely sure how the auth could have caused that error but I’m glad he’s up and running!