Verify traffic in Usage
1
Select the access and location
Open Usage, select the pass or rental, then choose the Network and
Location used by your deployment.
2
Select a time range
Choose the range that contains the request you are investigating. Usage overview refreshes for that scope.
3
Confirm the request was recorded
Read Total requests, Error rate, Requests over time, and Per-method analytics. View token summary shows the access aggregate and representative key details; it is not a per-token activity table.After a test request, the request count or method activity should increase
for the matching access, location, and range. Usage telemetry can arrive
after the response, so use the application’s status code for immediate
debugging.
Read published capacity in Limits
Open Limits and select the same access used by the application.
Limits can differ by access and product. Read the displayed values instead of encoding a tier table into your application. RPC caps apply per active location token where the table says so; Calls by token is the token-level usage view.
Investigate throttling
When the application receives a rate-limit response or cannot open more concurrent work:- Confirm the access, network, location, and token used by the failing client.
- Open Usage for the failure window and look for bursts, duplicate polling, retry loops, or unexpected methods.
- Open Limits for the same access and compare traffic with the relevant published tier limit. For RPC, check the active location token under Calls by token.
- Reduce concurrency, reuse connections, and close idle subscriptions.
- Retry only transient failures with bounded exponential backoff and jitter.