Two systems hit the same usage limit. Only one of them was spending it.

Описание и применение

Два автоматизированных конвейера остановились из‑за общей недельной лимиты использования аккаунта, но только один из них действительно потреблял квоту. Анализ показал, что лимит был совместно использован, и оптимальным решением является ожидание сброса или изменение лимита аккаунта, а не уменьшение нагрузки конвейера.

Задача

Two automated pipelines failed on the same day due to a shared weekly usage limit, but only one was actually consuming the quota.

Результат

The failure was caused by a shared account limit, not by the pipelines themselves. Adjusting per-run size would have minimal impact; the appropriate response is to wait for reset or adjust account provisioning.

Рабочий процесс

• 1. Observe HTTP 429 failures on both pipelines.
• 2. Check run ledger for failure_class: usage_limit.
• 3. Review account usage records for the week.
• 4. Determine that automation accounted for a small portion of total usage.
• 5. Update escalation rules to note that reducing per-run size is least effective.
• 6. Decide to either wait for reset, raise account limits, or adjust other account activity.
• 7. Document findings for future incidents.

Доказательства

Both returned the same response: HTTP 429 You've hit your weekly limit · resets Aug 31, 11pm (UTC)

Источник

The limit is scoped to the whole account, and the same account also carries interactive work unrelated to the automation.

Источник

The pipeline that stopped was not the one that had filled the quota.

Источник