vercel: Rate limit exceeded error on deploy

Hi all,

We have made a few improvements to our rate limiting system ensuring that the retry-after sliding window is correctly set making the rate limits reset on time.

As next steps we are making the CLI display more accurate information about the rate limit being hit https://github.com/zeit/now-cli/issues/2738 as well as documenting the limits on our website.

Thank you for the feedback @w33ble, we will add this as a note on the documentation about limits!

@Polyhistor can you help us sending information regarding your account/project to support@zeit.co so that we can take a closer look?

@tkdan235 on behalf of the ZEIT team I want to apologize for this bad experience. We are working on a few takeaways from this:

• Improving the error mesasge
• Improve the documentation about rate limits
• Reviewing whether the rate limits are currently appropriate for paid members
• We are working on reviewing why your outreach to support was unsuccessful so far

I appreciate you following up and we are working on a definitive resolution!

Is everyone in here now seeing a proper error message?

As of Now CLI 16.1.2, we’re now rendering the full error message from the API, which contains more details. No more client-side overwriting.

Hi all,

Aside from the changes to output useful rate limit messages on the CLI (already landed on the stable version), we have shipped a new improved section to our docs listing each of the limits https://zeit.co/docs/v2/advanced/platform/limits/

Any feedback is appreciated!

@422158 add ./coverage to .nowignore to fix the issue. You need to wait until your rate limit resets to re-test or contact a zeit employee to reset your limits.

I’m really sorry about the bad experience, we are still actively working to improve this situation. We already have a fix in progress for the erroneous message.

I will personally update this thread as soon as possible, thank you for your patience!

@Polyhistor it sounds like that could be related to caching (which we will also improve by actively invalidating as soon as you upgrade). Can you let me know if it’s still happening? Thank you!

Started hitting this yesterday, on the Unlimited plan. The message “Try again in X hours” comes along with it, where X just keeps going up. It’s unclear to us why we’ve started exceeding whatever limits are in place.

Seeing this too on a personal plan. I basically can’t interact with Now without hitting rate limits. My repo in GitLab is linked for automatic deployments and I get loads of comments from Now on the PRs saying “You are pushing commits at a very fast pace (accross the whole organization)” which isn’t true…