Some organizations received repeated emails that a spending notification threshold or hard limit had been reached, even after the first valid alert.
This was caused by a billing usage calculation that could briefly report daily spend as higher, then lower, then higher again. Each upward crossing looked like a new limit event, so the same notification was sent more than once.
API and market data services were not affected. Account spend limits themselves were not changed.
The usage calculation has been corrected so daily spend is counted once, and the billing notification path is operating normally again. No action is required. If you received duplicate threshold or hard-limit emails during this incident, you can ignore the extras.
No components marked as affected
Resolved
Some organizations received repeated emails that a spending notification threshold or hard limit had been reached, even after the first valid alert.
This was caused by a billing usage calculation that could briefly report daily spend as higher, then lower, then higher again. Each upward crossing looked like a new limit event, so the same notification was sent more than once.
API and market data services were not affected. Account spend limits themselves were not changed.
The usage calculation has been corrected so daily spend is counted once, and the billing notification path is operating normally again. No action is required. If you received duplicate threshold or hard-limit emails during this incident, you can ignore the extras.
