cloudflare / cloudflare/wrangler-action
Ratelimits on wrangler pages deploy
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 214
- PR merge metrics
- No merged PRs in 30d
Description
Hi, we have an opensource repo that has 2 pages builds for every PR.
Occassionally they fail with ratelimits. We don't have a lot of prs/deployments so we are not sure why they fail.
```
wrangler pages deploy --project-name=scuffle-docusaurus-docs --branch=pr/483 --commit-hash=ff05895b8290482f023bb0f1068fecf9795f15a2 --commit-dirty=true ./docs/build
```
See [this ci run](https://github.com/ScuffleCloud/scuffle/actions/runs/15364400854/job/43235469841?pr=483) for example.
A typical deploy command looks like such. We do not use cloudflare pages build system we use our own ci to build the javascript and all we use pages for is for hosting.
Our account id is: `6ca7d4e3d5c9496083876496fc36b8b0`
The two deployments are `scuffle-docusaurus-docs.pages.dev` and `scuffle-docrs.pages.dev`
```
✘ [ERROR] A request to the Cloudflare API (/accounts/***/pages/projects/scuffle-docusaurus-docs) failed.
Rate limited. Please wait and consider throttling your request speed [code: 10000]
📎 It looks like you are authenticating Wrangler via a custom API token set in an environment variable.
Please ensure it has the correct permissions for this operation.
```
Contributor guide
Research direction
Start with the wrangler pages deploy command and the linked GitHub Actions run, then compare the two deployments named in the report. Investigate the Cloudflare API rate-limit response and the request pattern from CI. Done means identifying a reproducible cause and documenting or verifying a mitigation for the failed deployments.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100