Understanding Auto Offer safety limits
Why seller automation needs per-minute, per-hour, per-day, capacity, and error-storm controls even on high plans.
Commercial limits and safety caps differ
A subscription may include a number of submitted offers per rolling day. Separately, the platform should maintain hard per-minute and per-hour caps that protect the account from loops or unexpected request floods.
An unlimited marketing label should never mean unlimited execution without a circuit breaker.
Count confirmed submissions
Usage accounting should reserve capacity before submission and reconcile the result. Retries for a request should not each consume a new commercial allowance if they belong to one idempotent operation, but genuinely new submissions should.
The owner needs visibility into used, remaining, and reset time.
Pause on abnormal behavior
Duplicate spikes, parser errors, authentication failures, repeated external rejections, and rapid tab loops are reasons to degrade or pause the affected action. A global kill switch and game-specific kill switch allow fast containment.
The user interface should explain the reason instead of only displaying Offline.