Limit handling
- At a limit, already-in-scope work can proceed. Only work that would exceed a dimension is blocked.
- Known over-limit requests return
422 workload_limit_exceededbefore excess processing. - If additional records are discovered asynchronously, processing pauses before consuming records beyond the allowance. The parent workflow becomes
blocked_by_limit, or a monitor becomesblockedwith that reason. - Counter updates and limit checks are atomic across concurrent processing, so parallel monitors cannot bypass the cap.
- AMLOK must agree a scope change and effective rate card before resuming. There is no automatic upgrade, additional fee or combination of different tier limits.
- A Signal month’s record allowance resets at the next UTC calendar month. Historical reports retain the earlier counts and limits. Resetting capacity does not waive the next month’s Signal charge or an unresolved source-count/scope limit.
as_of and keep a pagination cursor for a consistent progress snapshot. Start a fresh first-page read to see updated counts. This operational progress snapshot is separate from an immutable financial billing snapshot.
See complexity tiers, processing lifecycle and rate cards.