Nuxt 3 application throws 1102 errors since March 1st

Our Nuxt 3 project on Cloudflare pages has been throwing 1102 errors since Friday. Before this, our application did not encounter any errors. I did get an email that on March 1 all Cloudflare Pages projects would be migrated automatically. But that email did not suggest there was any reason to worry. We tried changing the CPU limit but once we did that our deployments were no longer working (Worker Pages deployment error and 1102 error. Error: Failed to publish your Function. Got error: workers.api.error.cpu_ms_limit_not_allowed_for_usage_model). Therefore we needed to create a new project to make sure we were still able to deploy changes.

I have already created an support ticket for this issue but I have not got any response to this. We highly appreciate any help, insights or suggestions on resolving this issue.

Hi @joey9,

We are currently reviewing and escalating internally similar tickets. I’ll DM you asking for your ticket ID.

3 Likes

An incident has been declared while we investigate these errors: Cloudflare Status - Issues changing CPU Limit for Cloudflare Workers and Pages

3 Likes

We changed our CPU limit back to the maximum amount and after this, our errors disappeared. We used to have the unbound setting active for our project so we think that on March 1st our CPU limit was set back from 30 seconds to 50 milliseconds. Our median CPU time was above that. So for anybody else who might be facing a similar issue: changing the CPU limit back to maximum seems to have resolved the 1102 errors for us.

Hi,

Thank you for letting us know. We’re glad that your were able to find a workaround for this issue and that now everything is working as expected. Also, the incident is now resolved as per Cloudflare Status - Issues changing CPU Limit for Cloudflare Workers and Pages

Please let us know if you need further assistance.

Hi @joey9, your topic has a solution here.

Let us know what you think of the solution by logging in and give it a :+1: or :-1:.


Solutions help the person that asked the question and anyone else that sees the answer later. Login to tell us what you think of the solution with a :+1: or :-1:.

Hi @joey9, your topic has a solution here.

Let us know what you think of the solution by logging in and give it a :+1: or :-1:.


Solutions help the person that asked the question and anyone else that sees the answer later. Login to tell us what you think of the solution with a :+1: or :-1:.

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