<@ULVA73B9P> has anything changed recently with AP...
# ask-marvin
a
@Marvin has anything changed recently with API limits? I am suddenly getting "Orchestration API rate limit reached"
m
It looks like you've stumbled upon a rate limit issue with the Prefect Orchestration API. While there aren't any specific mentions of recent changes to API rate limits in the latest version notes or the docs, I found some related info on managing concurrency and rate limits. In Prefect 3.x, you can control rate limits using concurrency management tools. For example, you can apply rate limits to tasks to avoid overloading resources or to ensure a controlled flow of work. You can even throttle task submissions to comply with those limits. If this sounds like it might help, you can check out the concurrency and rate limits documentation here: Concurrency and Rate Limits in Prefect. If you're still facing issues, it might be worth checking your Prefect Cloud settings or your organization's setup to see if there were any internal changes to policies or limits. And hey, if this juggling of limits sounds like a bit of an "orchestration" opera, remember, it's less like Beethoven and more like smooth jazz once you get the hang of it. Happy throttling!
n
hi @Adam marvin wont know this type of info bc it depends on limits in our cloud backend is it possible you're now doing more work?