All UsageAtlas guides

Factory Droid usage limits and reset times explained

Factory Droid usage limits and reset times explained

Read Factory's reported Standard and Core windows without mixing their allowances. Keep available limits and resets in view with UsageAtlas.

Quick answer

Use /limits in Droid and check the pool named in the response. UsageAtlas can display Factory's supported Standard and Core windows independently, along with reported resets and extra balances. Account billing formats can differ.

Download UsageAtlas for free

Free and open source for Windows, macOS, and Linux. No UsageAtlas account needed. View the source on GitHub.

Use limits for capacity and stats for history

Factory's CLI reference lists /limits and /stats as separate commands. Limits help you judge available capacity. Historical statistics answer how much work you already ran. The UsageAtlas Factory integration reads account capacity, not Droid's session statistics.

Keep each allowance with its own usage

Standard and Core can expose five-hour, weekly, or monthly windows. Read each window on its own. A user counter and an organization allowance are not automatically the same scope. UsageAtlas does not combine unrelated pools to create a percentage, and missing or unlimited allowances stay unknown.

Watch the window that is running low

Add your Factory key to UsageAtlas, open Limits, and configure an alert for supported windows. Reset times appear when Factory supplies them. The tracker is free and open source; Factory's account controls still manage overage and billing.

Questions, answered

Why does my account show older Standard or Premium counters?

Factory accounts can return different billing formats. UsageAtlas supports selected legacy counters as well as newer Standard and Core limits.

Does a missing reset mean the allowance never resets?

No. It means the response did not provide a usable reset time. Check Factory's own account view for details.