You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Recent Public API Rate Limiting Changes - Request To Reconsider Response Taken
#135
The new rate limiting and data volume threshold changes on the Public API feel like a significant overcorrection for an issue caused by a relatively small portion of users, but it will now impact the majority of customers who have been operating within the existing rules. For organizations like ours, the required adjustments will come with real costs in time, resources, and potentially business impact.
Changes of this magnitude typically require sufficient lead time so teams can plan and adapt without disrupting ongoing production work. In our case, this affects multiple teams that are already committed to current delivery timelines, and reallocating effort to address this will have downstream effects on those commitments.
I would encourage your team to revisit how this change is being rolled out and consider the operational and financial impact it will have on customers. Providing more time to adapt, or exploring alternative approaches, would help teams like ours implement the necessary changes responsibly without creating unnecessary disruption.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
The new rate limiting and data volume threshold changes on the Public API feel like a significant overcorrection for an issue caused by a relatively small portion of users, but it will now impact the majority of customers who have been operating within the existing rules. For organizations like ours, the required adjustments will come with real costs in time, resources, and potentially business impact.
Changes of this magnitude typically require sufficient lead time so teams can plan and adapt without disrupting ongoing production work. In our case, this affects multiple teams that are already committed to current delivery timelines, and reallocating effort to address this will have downstream effects on those commitments.
I would encourage your team to revisit how this change is being rolled out and consider the operational and financial impact it will have on customers. Providing more time to adapt, or exploring alternative approaches, would help teams like ours implement the necessary changes responsibly without creating unnecessary disruption.
All reactions