This may be a transient error

Help
1

I’m continuously getting this error. I used an old build that worked before, but now it doesn’t work anymore. I suspect it’s a Vercel issue, but I can’t submit a ticket with the Hobby Plan. This is a frustrating experience…

image
image1228×240 19.4 KB

2

Can you share the deployment link?

3

Last one i tried: https://trace-mail-41j049r1r-appelmoesjes-projects.vercel.app

I can share more if necessary

4

Thanks! Can you share following details:

  1. Are you using vercel.json with excludeFiles ? If so, what values are you using? Docs.
  2. Have you recently added any node modules to your package.json ?
  3. Can you turn on Customer Success Code Visibility in your project’s Security Setttings so that we can inspect the source code?
  4. Does a redeploy without build cache work?
5
  1. No, I’m not using excludeFiles in my vercel.json
  2. For almost 3 weeks I did not change the package.json
  3. I can’t find this setting in my project or in the Vercel docs?
  4. I tried redeploys of new code and reverted back to old (previously working) builds without using build cache but nothing seems to work
8

Thanks! Let us investigate this and get back to you.

1 Like
9

I appreciate your help, but this is becoming quite frustrating as it’s taking longer than expected, and we’re currently unable to make any updates to the project. Any updates or concrete next steps would be really helpful at this point. Thanks for your time.

10

This error may happen due to including large dependencies, non optimised function size etc which has 250 mb limit.

To identify the potential culprit on your end, you can run vercel build locally between commits and inspect the output files in .vercel folder to compare the size.

11

I checked the logs in Vercel, and while the build size is close to the limit, it hasn’t exceeded it. When I do hit the limit, a different error is displayed. I also verified the size locally by checking the .vercel folder, and it’s within the allowed range.

12

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.

13

Hi,

Thank you for your patience!

We’ve identified this issue is related to the bundle size limit. To fix this issue, we recommend following the Bundle Size Limits in our documentation here: Choosing a Runtime

This error wasn’t very descriptive previously, but we will look to update this in the near future. Thanks!

2 Likes