Review usage and limits

Distinguish admission limits from policy and upstream errors.

Before you start

Choose a bounded time window and the account or environment whose usage you are investigating.

Procedure

1. Open usage and limits in the console and confirm the scope and reporting window.

2. Compare the usage result with the configured limit and any admission reason on the affected request.

3. Check whether a rejection is a quota, rate, policy, or upstream failure before changing configuration.

4. For an approved limit change, use the supported administration flow and verify subsequent admission with a test request.

Verify the result

Compare the new request outcome with the limit state and audit evidence. Aggregated usage does not explain a particular denial by itself.

If it does not work

If usage data is delayed or unavailable, preserve the request reason and reporting window. Do not infer zero usage from missing data.

Read the related concept or consult the Admin API for exact request fields.

Implementation reference

Read the source contract.