twitter v2 api has route specific limits relative to the number of authorized accounts, and its possible for a single bot reporting at a high frequency (e.g. a sales pump) to "overflow" the limit derived just from its authorization, and start eating into limits that should be provisioned for other bots.
[ ] apply for increased api tier
[ ] book-keep account specific limit + exhaustion and stop creating tweets when exhausted
[ ] consider throttling + batching strategies during periods of high activity
twitter v2 api has route specific limits relative to the number of authorized accounts, and its possible for a single bot reporting at a high frequency (e.g. a sales pump) to "overflow" the limit derived just from its authorization, and start eating into limits that should be provisioned for other bots.