# Getting a server 500 error on adding a user to our team

**URL:** <https://community.hubspot.com/t/getting-a-server-500-error-on-adding-a-user-to-our-team/108512>\
**Category:** Account & Settings\
**Tags:** free\
**Created:** [June 3, 2024, 3:01pm UTC](https://community.hubspot.com/t/getting-a-server-500-error-on-adding-a-user-to-our-team/108512 "2024-06-03T15:01:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![SHoward2](https://avatars.discourse-cdn.com/v4/letter/s/f9ae1b/32.png) [@SHoward2](https://community.hubspot.com/u/SHoward2)\
**Post date:** [June 3, 2024, 3:01pm UTC](https://community.hubspot.com/t/getting-a-server-500-error-on-adding-a-user-to-our-team/108512/1 "2024-06-03T15:01:57Z")

</div>

We are evaluating Hubspot to move to a paid version.

We have used 2 of the 5 users. We are on the EU servers.

When we attempt to add a third user, we get a 500 response from the EU servers. But chat support says we need to post here. For what is clearly a 500 server error.

Here is the payload from our response to add a user:

{  
“status”: “error”,  
“message”: “internal error”,  
“correlationId”: “b7059b6a-fc0a-419e-a52f-a2faec5cc831”  
}  
Steps to recreate:  
- ensure Chrome browser is latest

- be on the EU servers

- log in in icognito mode to ensure cookies aren’t the issue

- Got to Teams and Users

- Add a new user.

- Monitor the browser console to see the 500 response to the Post event.

---

<div class="post-metadata">

**Author:** ![SHoward2](https://avatars.discourse-cdn.com/v4/letter/s/f9ae1b/32.png) [@SHoward2](https://community.hubspot.com/u/SHoward2)\
**Post date:** [June 3, 2024, 3:48pm UTC](https://community.hubspot.com/t/getting-a-server-500-error-on-adding-a-user-to-our-team/108512/2 "2024-06-03T15:48:23Z")

</div>

This appears to be fixed now.

---

<div class="post-metadata">

**Author:** ![Lucila-Andimol](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/lucila-andimol/32/69276_2.png) [@Lucila-Andimol](https://community.hubspot.com/u/Lucila-Andimol)\
**Post date:** [June 5, 2024, 11:16am UTC](https://community.hubspot.com/t/getting-a-server-500-error-on-adding-a-user-to-our-team/108512/3 "2024-06-05T11:16:52Z")

</div>

Hey @SHoward2

in general 500 are returned when HubSpot’s processing limits have been met.

This sure is temporary, and is propably fix if you wait a couple of minutes or to the next day.

Glad to see you have solve it, just leaving this info for future reference and other users.

---

<div class="post-metadata">

**Author:** ![SHoward2](https://avatars.discourse-cdn.com/v4/letter/s/f9ae1b/32.png) [@SHoward2](https://community.hubspot.com/u/SHoward2)\
**Post date:** [June 5, 2024, 11:45am UTC](https://community.hubspot.com/t/getting-a-server-500-error-on-adding-a-user-to-our-team/108512/4 "2024-06-05T11:45:49Z")

</div>

Hi Maria,

Sending a 500 on a processing limit is really bad practice. It may be true but it would surprise me as Hubspot has really solid APIs. A 500 is supposed to denote a server failure event.

There are codes to denote events such as you describe.

I defer to your experience. Another way to put this that would be a valid 500 code is Hubspot has micro-failures periodically that get auto-detected and those workers/services get periodically reset when that happens.

Sean

---

<div class="post-metadata">

**Author:** ![mangelet](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/mangelet/32/83031_2.png) [@mangelet](https://community.hubspot.com/u/mangelet)\
**Post date:** [June 5, 2024, 1:41pm UTC](https://community.hubspot.com/t/getting-a-server-500-error-on-adding-a-user-to-our-team/108512/5 "2024-06-05T13:41:51Z")

</div>

@SHoward2 adding to what @Lucila-Andimol mentioned, a 500 error is a generic internal server error, meaning the issue is on Hubspot’s side, not necessarily your setup.

This error message doesn’t give specific details about the problem but is **most likely a temporary glitch**. There could be an issue with Hubspot’s servers causing unexpected behaviour.

**Often, this gets resolved without any intervention.**

Unfortunately, this isn’t uncommon, as you can see in the following screenshot…

 ![Screenshot 2024-06-05 at 15.28.03.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/0/9/09a0fc85ca779a78038b90b50034078d24eebc27.png)

Disclaimer: My initial reaction was to **check rate limits** , as the number of calls your app can make depends on your account subscription and whether you’ve bought an API add-on…

---

<div class="post-metadata">

**Author:** ![SHoward2](https://avatars.discourse-cdn.com/v4/letter/s/f9ae1b/32.png) [@SHoward2](https://community.hubspot.com/u/SHoward2)\
**Post date:** [June 5, 2024, 3:00pm UTC](https://community.hubspot.com/t/getting-a-server-500-error-on-adding-a-user-to-our-team/108512/6 "2024-06-05T15:00:14Z")

</div>

Thanks Martin!

This was actually through their web interface as a logged in user, not an API call. So I was surprised to see a 500 server error in the javascript console and in the fetch on my browser inspect.

It definitely did resolve itself. Thank you.
