Frequent 504 GatewayTimeout errors when using

  • 24 March 2024
  • 2 replies



We are testing our Miro implementation and are seeing frequent 504 GatewayTimeout responses.

Seems to frequently occur when we are creating a team

Happy to provide more details.

Any insight into what could cause frequent 504 GatewayTimeout errors to come back from the api would be greatly appreciated. 

Thank you.

2 replies

Userlevel 3
Badge +1

Hi @Robert Lewis,

Thank you for reaching out. I’m sorry you’re seeing these errors from the Miro side. Could you please provide me with a bit more details to help our team identify the issues?

How many API calls are you normally making within a specified amount of time? Are you also populating the team name parameter as well? 

I will take this to our engineering team and let you know once I hear back. 

Userlevel 3
Badge +1

Hi @Robert Lewis 

I’ve just tried to reproduce this on my own. I’ve created 10 teams in an org and all got 201 responses (success). 

Have you noticed that the API call is taking too long (i.e. more than 60 seconds) since that can cause a 504 error. Or does it seem to work quickly and just return a 504? It would help us to understand when you are seeing the error.

Please let me know if you have more details to help diagnose this issue further.