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
I think team admins should know when this happens, because their bots will stop working when it does. See OpenAI's error codes page for the different types of rate limits.
We can use regex to catch specific 429 messages (they seem to be static) and send an email to all users on the team that have super admin or team admin access.
A thought: High utility of a specific provider will increase the chance of it being rate limited, since limits exists on organization and project levels. We can be a bit more proactive and inform users about this potential issue when we detect high utility of a single provider. Maybe. Not sure if this should be a documentation thing or if we should build something into the platform.
The text was updated successfully, but these errors were encountered:
Regarding this issue: https://dimagi.sentry.io/issues/5986776238/?alert_rule_id=14063560&alert_type=issue¬ification_uuid=571a9dea-ea23-4dc3-bcf1-f9b426f90a76&project=4505001320316928&referrer=issue_alert-slack
I think team admins should know when this happens, because their bots will stop working when it does. See OpenAI's error codes page for the different types of rate limits.
We can use regex to catch specific 429 messages (they seem to be static) and send an email to all users on the team that have super admin or team admin access.
A thought: High utility of a specific provider will increase the chance of it being rate limited, since limits exists on organization and project levels. We can be a bit more proactive and inform users about this potential issue when we detect high utility of a single provider. Maybe. Not sure if this should be a documentation thing or if we should build something into the platform.
The text was updated successfully, but these errors were encountered: