Failed to publish your Function. Got error: Error: Script startup exceeded CPU time limit.

[shiyuhang0]

I am using nextjs and prisma data proxy to connect to a database.
Then I deploy to cloudflare pages but failed with Script startup exceeded CPU time limit.

I don't know if it is the problem of my project or the work_js generated by next-on-pages.

[mihazs]

I'm having the same issue right now, i'm not able to update my application because of that.

In my case, the _worker.js file inside .vercel/output/static folder, has 7.2MB, which is very huge for a worker script.

According with : https://developers.cloudflare.com/workers/platform/limits/#worker-startup-time

Script size can impact startup because there’s more code to parse and evaluate.

In my tests, the _worker.js file easily increases a lot the size in every new build with new features, so the script startup will exceed CPU time limit all the time.

For me, this is a deal breaker. I came to the conclusion that cloudflare pages and next.js only works for tiny projects at this moment. Right now, I'm working to get my project out of the cloudflare and considering Vercel, netlify or open-next for deploy to AWS.

If you want a fast solution, probably cloudflare wouldn't fit :/

[simonschwitzky]

Sharing this experience with a very small project, 5 pages, not many additional dependencies and 2 pages using little data from getServerSideProps.

[xMuratY]

I just created a layout component (just some html no server side things) and then created dummy pages with the calling layout. After duplicating the pages this problem appeared. Can publish with removing some of the dummies.

//edit: build log

2023-02-15T02:30:20.873828Z ▲ info - Generating static pages (0/2)
2023-02-15T02:30:20.87394Z ▲
2023-02-15T02:30:20.974761Z ▲ info - Generating static pages (2/2)
2023-02-15T02:30:20.975103Z ▲
2023-02-15T02:30:20.99126Z ▲ info - Finalizing page optimization...
2023-02-15T02:30:20.991593Z ▲
2023-02-15T02:30:20.996341Z ▲
2023-02-15T02:30:20.996627Z ▲
2023-02-15T02:30:21.038888Z ▲ Route (pages) Size First Load JS
2023-02-15T02:30:21.0394Z ▲ ┌ ℇ / 425 B 73.8 kB
2023-02-15T02:30:21.039665Z ▲ ├ /_app 0 B 73.4 kB
2023-02-15T02:30:21.039867Z ▲ ├ ○ /404 181 B 73.6 kB
2023-02-15T02:30:21.040038Z ▲ ├ ℇ /api/auth 0 B 73.4 kB
2023-02-15T02:30:21.040171Z ▲ ├ ℇ /auth/signin 3.18 kB 78.6 kB
2023-02-15T02:30:21.040298Z ▲ ├ ℇ /auth/signup 3.22 kB 78.7 kB
2023-02-15T02:30:21.040421Z ▲ ├ ℇ /dashboard 1.87 kB 90.2 kB
2023-02-15T02:30:21.040575Z ▲ ├ ℇ /dashboard/management 1.89 kB 90.2 kB
2023-02-15T02:30:21.040695Z ▲ ├ ℇ /dashboard/management/keys 1.89 kB 90.2 kB
2023-02-15T02:30:21.040805Z ▲ ├ ℇ /dashboard/management/updates 1.89 kB 90.2 kB
2023-02-15T02:30:21.040914Z ▲ ├ ℇ /dashboard/management/users 1.89 kB 90.2 kB
2023-02-15T02:30:21.041031Z ▲ ├ ℇ /dashboard/order 1.87 kB 90.2 kB
2023-02-15T02:30:21.041154Z ▲ └ ℇ /dashboard/recent 1.87 kB 90.2 kB
2023-02-15T02:30:21.041271Z ▲ + First Load JS shared by all 76.9 kB
2023-02-15T02:30:21.041384Z ▲ ├ chunks/framework-2c79e2a64abdb08b.js 45.2 kB
2023-02-15T02:30:21.041504Z ▲ ├ chunks/main-809835cec98db2ac.js 26.9 kB
2023-02-15T02:30:21.041613Z ▲ ├ chunks/pages/_app-891652dd44e1e4e1.js 296 B
2023-02-15T02:30:21.041719Z ▲ ├ chunks/webpack-0b5d8249fb15f5f3.js 939 B
2023-02-15T02:30:21.042024Z ▲ └ css/837114518d7a7749.css 3.55 kB
2023-02-15T02:30:21.042201Z ▲
2023-02-15T02:30:21.042468Z ▲ ƒ Middleware 48.4 kB
2023-02-15T02:30:21.042619Z ▲
2023-02-15T02:30:21.042734Z ▲
2023-02-15T02:30:21.042856Z ▲ ℇ (Streaming) server-side renders with streaming (uses React 18 SSR streaming or Server Components)
2023-02-15T02:30:21.042964Z ▲ ○ (Static) automatically rendered as static HTML (uses no initial props)
2023-02-15T02:30:21.043081Z ▲
2023-02-15T02:30:21.043193Z ▲
2023-02-15T02:30:21.985327Z ▲ Collected static files (public/, static/, .next/static): 19.694ms
2023-02-15T02:30:21.985934Z ▲
2023-02-15T02:30:22.352255Z ▲ Using TypeScript 4.9.5 (local user-provided)
2023-02-15T02:30:22.352633Z ▲
2023-02-15T02:30:25.316304Z ▲ Build Completed in .vercel/output [31s]

[GregBrimble]

This Worker startup time limit is unfortunately unrelated to this project, and is just a fundamental limit of the Workers platform: https://developers.cloudflare.com/workers/platform/limits/#worker-startup-time

If you can, try to move any work you do into request handlers rather than having it in global scope, as this moves the work from startup time to request time which may help here.

[Rigo-m]

Why isn't the CPU limit following the bundled/unbounded rules?
I.e.: I tried changing to unbounded mode (30s startup time limit vs 50ms CPU Time Limit), but I got the same error after 2 seconds.

[nitaking]

@GregBrimble

If you can, try to move any work you do into request handlers rather than having it in global scope, as this moves the work from startup time to request time which may help here.

Can you give us a specific example?

I understand why this is closed, but it has become an immediate problem faced by sites using cloudflare pages and Nextjs and is an issue that should be addressed quickly to resolve.

Cloudflare team should provide some kind of concrete solution.

[dario-piotrowicz]

@nitaking Yeah this is a real issue and something that I believe very often developers can't do much about (especially if they include third party code which can do things at startup anyways).

We've actually already got a solution for this and we should release it soon, but before we can do that some changes need to be made in wrangler and I believe Greg is looking into that.

The solution will be next-on-pages splitting the code appropriately and lazy loading route code so that it is run only when needed resulting in a much lighter startup processing, so from a developer point of view you will hopefully only have to upgrade the next-on-pages package and things should just work 🙂👍

[aufalmarom]

got the same issue please help us guys, i was deployed next js project at cloudflare pages

[ynishimura]

I am experiencing the same problem. Is there a workaround?

[Rigo-m]

We've actually already got a solution for this and we should release it soon, but before we can do that some changes need to be made in wrangler and I believe Greg is looking into that.

Since this problem is present in other metaframeworks as well (e.g.: nuxt3 with nitro), would you mind sharing your findings so that it's possible to pass on these improvements in these other metaframeworks as well?

[uglyrobot]

Blocked me from using Pages today as well. Off to Vercel...