Hey all, I work at a Boston startup that utilizes Prefect very heavily and have a question about Prefect's API rate limiting. In the past, we used to have no control on the amount of concurrent calls we would make to Prefect. We then started to get rate limited by Prefect as our requests would come in large bursts that may have been overloading Prefect. We then started to only allow one concurrent Prefect call at a time to reduce possible lost of requests as a result of rate limiting. This then proved too small of an amount and we've boosted it up to five concurrent calls. We are currently having trouble with this being too small of an amount and are looking to further boost the number. Our question is whether there are specific limits we should be aware of and work around to prevent the API rate limiting that has affected us poorly in the past.

Hi @Shea O'Rourke - there are no specific limits on API traffic but we do employ automatic rate limiting in burst situations like you've described above. I've asked the team for a little more info on when that kicks in and will get back to you asap 🙂

Hey Nicholas, thanks for the response! Just circling back to this to see if you have gotten any more specific information from the team, thanks!

Ah sorry - thanks for the reminder; I've spoken with the team and they're not able to provide specific information further than that we have very generous limits on burst traffic. If you continue to run into issues, I can put you in touch with someone on our Sales team that can talk you through what resources we have available to work with you