vercel: Timeout while verifying instance count

Constantly getting this error when running now scale xyz:

> Error! An unexpected error occurred in scale: Error: Timeout while verifying instance count (10m)
    at waitForScale (/snapshot/repo/dist/now.js:8878:13)
    at <anonymous>

About this issue

Original URL
State: closed
Created 6 years ago
Reactions: 10
Comments: 34 (6 by maintainers)

Most upvoted comments

This should never happen again in the latest both stable and canary releases! Please reopen if anybody else experiences this issue.

javivelasco on Apr 19, 2018

I get the same on sfo1 trying to deploy anything with now

rwboyer on Apr 8, 2018

Same here. Just sent you guys an email before heading here to check the conversation.

screen shot 2018-04-08 at 6 53 08 am

nnennajohn on Apr 8, 2018

Between 40% and 80% of my deploys fail (it varies from day to day( on BRU1 due to this problem. I’m running out of options.

Today I’ve had 2 successful deploys out of 12 and still going.

antony on May 28, 2019

This should never happen again in the latest both stable and canary releases! Please reopen if anybody else experiences this issue.

@javivelasco This should be reopened. I have instance verification timeouts for latest stable release versions in bru1. Tested versions 14.2.0 on up all the way to lts 15.3.0.

It feels like there just aren’t enough resources allocated for bru1 anymore:

Is this true?

moolbits on May 30, 2019

We have not been able to scale up BRU1 on the first try for about a month.

s-r-jones on May 22, 2019

i, too, am getting this error:

⠼ Verifying instances in sfo1> Error! An unexpected error occurred!
  Error: Timeout while verifying instance count (10m)
    at waitForScale (/snapshot/repo/dist/now.js:8446:13)
    at <anonymous> Error: Timeout while verifying instance count (10m)
    at waitForScale (/snapshot/repo/dist/now.js:8446:13)
    at <anonymous>

there are no errors in my code, i ran a standard JS task to clean and report any JS error, which came back with none.

benjtinsley on Apr 13, 2018

Sorry, getting the same with bru1 and sfo1 since last night.

update: I also had broken code (third party dep) and it works fine after fixing that, same as @heymartinadams. This is a non issue for me!

Or rather… this is a messaging issue.

antony on Apr 10, 2018

+1, both bru and sfo, timeout

akabab on Apr 10, 2018

Yes indeed, @nnennajohn! 😎

heymartinadams on Apr 9, 2018

Ah! There was an error in my code, which I only discovered by deploying via localhost instead of now. Once fixed, I no longer received a timeout. So it might only occur if there’s an unrelated bug.

/Users/__USER__/Apps/__MY_APP__/node_modules/graphql-yoga/node_modules/graphql-tools/dist/schemaGenerator.js:341
                throw new SchemaError(typeName + "." + fieldName + " defined in resolvers, but not in schema");
                ^

heymartinadams on Apr 11, 2018

+1 Getting when deploying to bru1

hakonkrogh on Apr 5, 2018