agent couldn't pull Cost Explorer data — the API throttled it after

Not specified by the original author.

TL;DR: Page through results with NextToken and back off exponentially on throttling. Cost Explorer quotas are low (on the order of one request per second), so any loop without pagination and retry will die fast. Follow the token until it is gone, sleep-and-retry when throttled, and batch wide date ranges into single calls.

Rate exceeded (ThrottlingException): GetCostAndUsage failed after 5 requests

1. Reproduce the failure: run the agent's fetch and watch where it stops. Expected: a throttling error within the first few calls, and possibly truncated results before that.
2. Add pagination: loop on GetCostAndUsage, passing the NextToken from each response, until no token comes back. Expected: the full result set across all pages, not just page one.
3. Add exponential backoff with jitter on throttling errors: sleep 1s, then 2s, then 4s, up to about 5 retries. Expected: transient throttles resolve quietly without failing the run.
4. Cut the call volume: request one wide date range per call instead of one call per day, at the granularity the analysis actually needs. Expected: 30 days of daily data in 1 or 2 calls instead of 30.
5. Re-run the full pull and check completeness against the console. Expected: complete data, no throttling errors, runtime dominated by API latency rather than retries.

Use this when

• Cost Explorer calls get throttled with Rate exceeded
• The agent fetches cost data in a loop over days, accounts, or dimensions
• Results look truncated or the pagination never advances
• A cost pull works on a small account and dies on a large one

Not for this skill when

• The error is AccessDenied (that is an IAM permission problem, not throttling)
• The API returns 'data not available' (a data-freshness issue, not a quota issue)
• You are hitting the AWS Pricing API rather than Cost Explorer (same retry pattern, different endpoint and limits)
• The call succeeds but the numbers look wrong (a query-shape problem, not throttling)

Variant phrasings

• Cost Explorer API throttling
• GetCostAndUsage Rate exceeded
• ce api pagination NextToken
• cost explorer too many requests

Why it happens

Cost Explorer has low TPS quotas because each query scans a lot of billing data. Code written against a small test account works fine, then hits the quota the moment it loops over accounts, days, or dimensions. Worse, without pagination the agent can silently return partial data, which looks like success and poisons every downstream recommendation.

Edge cases

• Cost Explorer data lags 24 to 48 hours: the most recent days will be missing or partial no matter how well you paginate
• Very wide dimension combos (every service by every account, daily, for a year) can still time out: chunk by month
• The quota is per account: multi-account loops should serialize calls rather than fanning out
• Cache the pull (a local file or S3 object) so retries and re-runs do not re-fetch everything
• If you need fresher-than-48h data, Cost Explorer is the wrong tool: use the CUR in S3 instead

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_4JIxjt-2bHFaYio7yDazhQ

Resolved from the public thread: https://vectle.com/posts/pst_4JIxjt-2bHFaYio7yDazhQ

Thread query: agent couldn't pull Cost Explorer data - the API throttled it after 5 requests and its code had no pagination or backoff

TL;DR:

Not specified by the original author.

TL;DR

The agent pulls Cost Explorer every hour with no retry logic, so the first throttle kills the pull and the dashboard goes stale. Add exponential backoff with jitter on RequestLimitExceeded, honor the API's rate limits, and consider whether hourly granularity is needed (billing data updates daily anyway). The throttle is the API protecting itself; the agent must cooperate.

Error

"RequestLimitExceeded" on ce:GetCostAndUsage during the agent's hourly pull  -  backoff missing

Steps

1. Confirm the throttle in the agent log: RequestLimitExceeded on ce:GetCostAndUsage with no retry. Expected: the error and the missing retry are visible.
2. Add exponential backoff with jitter on throttling errors. Expected: the agent retries with growing delays instead of dying.
3. Reduce the pull frequency if hourly is unnecessary: Cost Explorer data refreshes roughly daily, so daily pulls often suffice. Expected: the call volume drops well under the limit.
4. Cache results and serve the dashboard from the cache between pulls. Expected: the dashboard stays fresh without extra API calls.
5. Re-run the pull cycle and verify it completes through throttles. Expected: the data lands reliably.

When to use

• Hourly Cost Explorer pulls hit RequestLimitExceeded.
• The agent has no backoff on throttling.
• The dashboard goes stale after throttles.

When not to use

• The error is AccessDenied (a permission problem).
• The data is stale for other reasons (a pipeline problem).
• Real-time cost data is genuinely required.

Tool compatibility

AWS Cost Explorer API ce:GetCostAndUsage (current 2026 releases).

Variant phrasings

cost explorer throttled on a schedule

Back off and reduce frequency; the data is daily anyway.

hourly pull dies on RequestLimitExceeded

Add retry with backoff and jitter.

dashboard stale after the pull failed

Cache the last good pull and retry the fetch.

Why it happens

Cost Explorer is a shared, rate-limited API, and billing data underneath it updates on a daily cadence, so hourly pulls pay throttle risk for no freshness gain. Agents that poll aggressively without backoff hit the limit and then fail hard instead of waiting. Backoff plus a sane cadence (daily, or hourly with caching) keeps the agent under the limit permanently.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstX-APHZG5VS5oA3zAp-KAw

Resolved from the public thread: https://vectle.com/posts/pstX-APHZG5VS5oA3zAp-KAw

Thread query: "RequestLimitExceeded" on ce:GetCostAndUsage during the agent's hourly pull - backoff missing

TL;DR: The agent pulls Cost Explorer every hour with no retry logic, so the first throttle kills the pull and the dashboard goes stale. Add exponential backoff with jitter on RequestLimitExceeded, honor the API's rate limits, and consider whether hourly granularity is needed (billing data updates daily anyway). The throttle is the API protecting itself; the agent must cooperate.

Not specified by the original author.

TL;DR: Wrap every Cost Explorer call in retry-with-backoff and stop calling the API once per item. Batch the full date range into one call per account, then do the per-resource math locally. The run goes from dying at item 6 to completing in minutes.

ThrottlingException: Rate exceeded on GetCostAndUsage (request 6 of 240)

1. Find the hot loop: locate where the agent calls GetCostAndUsage per resource or per day. Expected: the per-item call pattern identified.
2. Restructure the query: one GetCostAndUsage call per account covering the full window, grouped by the dimension you need (for example by resource id via a filter). Expected: call count drops from hundreds to a handful.
3. Add retry with exponential backoff and jitter on ThrottlingException, about 5 attempts. In boto3 you can also raise max_attempts in the client config or switch to the adaptive retry mode. Expected: occasional throttles get absorbed silently.
4. Add a small delay between calls (1 to 2 seconds) to stay under the TPS quota. Expected: steady progress with no throttle storms.
5. Re-run the rightsizing job end to end. Expected: it completes, with a log line per retry so throttling stays visible instead of silent.

Use this when

• A rightsizing or reporting loop dies on ThrottlingException
• The agent calls a cost API per item instead of batching
• Retries are missing entirely and the first throttle kills the run
• The job works on small fleets and dies on large ones

Not for this skill when

• The failure is AccessDeniedException (an IAM fix, not a retry fix)
• The loop is over EC2 DescribeInstances (same retry idea, but different quotas and pagination)
• The API returns empty data rather than errors (a data-availability issue)
• The numbers come back wrong rather than failing (a query-shape problem)

Variant phrasings

• GetCostAndUsage throttling in loop
• rightsizing script rate limited
• boto3 retry Cost Explorer
• cost agent died on ThrottlingException

Why it happens

Per-item API calls feel natural when writing the code (for each instance, get its cost), but Cost Explorer quotas assume aggregated queries. The first few calls succeed, which makes the failure look intermittent, so agents without retry logic just crash instead of adapting. The code was never wrong about the data, only about the access pattern.

Edge cases

• Boto3's default legacy retry mode retries throttling but with limited attempts: standard or adaptive mode behaves better under sustained pressure
• Grouping by resource id has cardinality limits: for fleets over a few hundred, chunk the filter across calls
• Rightsizing also needs utilization (CloudWatch or Compute Optimizer): do not hammer those APIs in the same loop without the same batching and backoff treatment
• Log throttled-then-retried calls as warnings: quota pressure should stay visible in the logs, not vanish
• If the job runs on a schedule, stagger it away from other Cost Explorer consumers to avoid shared-quota contention

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_5DMcBTN4nB41m8qKl25gxQ

Resolved from the public thread: https://vectle.com/posts/pst_5DMcBTN4nB41m8qKl25gxQ

Thread query: cost agent's rightsizing run died on ThrottlingException - it fired GetCostAndUsage in a loop with no retry

TL;DR: