[▲ Vercel Community](/) · [Categories](/categories) · [Latest](/latest) · [Top](/top) · [Live](/live)

[Feedback](/c/feedback/8)

# Check on GitHub PR not updating after build-rate-limit failure

42 views · 0 likes · 1 post


Laurence "DC5B" Lord (@ll782) · 2025-11-19

## **Summary of issue (bug)**

On a GitHub PR with a Vercel deployment check, when the check fails due to a “paid-per-hour” rate limit, the PR enters a broken state, since the check does not get updated by latest deployment.

## **Expected behaviour**

* “Details” link (in GitHub check) go to related deployment (in Vercel dashboard)
* Message about the failure is visible on Vercel deployment screen
* Redeployment option is available on Vercel deployment screen
* Changes to the state of the Vercel deployment are reflected on the GitHub check

## **Actual behaviour**

* “Details” link go to [https://vercel.com/acme?upgradeToPro=build-rate-limit](https://vercel.com/ledgerhq?upgradeToPro=build-rate-limit)
* Redeployment for the PR/branch does not update GitHub check
* Fresh commit needed to retrigger checks

## Further details

### **Comment on PR from Vercel (bot)**

> Deployment failed with the following error:
>
> ```
> Resource is limited - try again in 55 seconds (more than 450, code: "api-deployments-paid-per-hour").
> 
> ```
>
> Learn More: [https://vercel.com/acme?upgradeToPro=build-rate-limit](https://vercel.com/ledgerhq?upgradeToPro=build-rate-limit)

### **Bad target for details Link on check** 

Normally the “Details” link against a failing Vercel deployment check goes to the failed deployment with the option to redeploy. Sadly the “Details” link goes to the `upgradeToPro=build-rate-limit` URL instead

### **Vercel deployment check in GitHub does not update**

Normally, updating the related deployment changes the state of the check in GitHub – to pending, success or failure – depending on the state of the redeployment.