glad to hear it. thanks for writing back in and sharing your that your issue was resolved.
I’m having the same issue with my site. Can’t get anything to deploy but it builds fine.
This seems to be the site id:
438a4ca6-aae5-43ff-b946-65ed77c2298e
We’ve excluded you from the rollout as well.
@hrishikesh I encountered the same error on my site. Could you also exclude it?
site ID: ec433035-f6d4-44d7-909f-c01089c3fa46
Done, it’s excluded.
Thank you. It is now able to be deployed.
1 Like
I am having the same issue deploying the site with nx mono repo nextjs project
site id : a5450fa1-bf2a-460b-92bb-1d0b45f9734b
site name : nclex-dev
can you help me with it
Hi, @Meghraj-official. I’ve added that site to the exclusion list as well. Would you please test building again now?
Howdy @luke, looks like I’m facing this issue on our sites as well.
Currently trying to build the following:
Site ID: 79730f44-8e64-427a-b2c7-f275d08b7f6d
Site Name: gcollective
Framework: Next.js@15.1.3
Any chance you’re able to exclude this site? If possible, could you exclude all the sites in my organization alongside it?
I’m very eager to learn what exactly is behind this issue, is there anywhere I can read about it?
Thanks,
Owen
I’ve excluded that site. The remaining sites in your account seem to be old (the last publish is on Dec 10, 2024 which is alread a month old). Are you working on other sites? It would be useful to have a specific list of sites to exclude instead of excluding all of them.
As for the issue, we’re not quite sure yet unfortunately.
Thank you for doing that. The four other sites I’m primarily worried about are the following:
7ac29219-b59f-48b3-a21f-3677292e9ed1
b0c1c14d-5e87-4c05-87ad-257db8abb728
e9a6db69-757e-4145-892c-7a39c2146d9d
fdfd6fbb-64a5-4565-845d-ec40736325ca
Specifically, gcollective-v2 is failing on deploy and is due for launch tomorrow.
Can you please exclude these four as well? Thank you
It’s not working even now
I’m sorry, I believe I am having the same problem.
Site id ea091e05-9994-4acb-874a-59bfe6138262
Is there a self-service way to just opt out of all this?
@JohnHilton there’s no way to self-serve, but I’ve opted you out of the flag that may be causing this issue. Could you try again?
@sid.m really appreciate the quick action on this - thank you. Can confirm that this site is now deploying as expected.
Frankly, 
Nice work.
1 Like
@JohnHilton Great to hear, thanks so much for letting us know!
Ah sorry, turns out we have another site also with the same problem. Could you opt this one out too please?
e1b1ed31-6b28-4473-835a-f99717561741
Many thanks.
I’m afraid this is turning into a bit of a nightmare.
The hitherto working site
1e1bfc09-eda6-4764-bf6a-63a643627e05
has, as of this afternoon, developed the same problem. I’m playing whac a mole between my instances - as soon as one works, another dies!
Update. This is interesting. The error seems to be associated with editing a single file on GitHub through their edit interface. This breaks the site. BUT clearing the cache for the site seems to fix it. It’s hard to test because obviously I’m a bit loathed to break my working deploys, but it looks like maybe the issue is with cached data somehow?
@JohnHilton It looks like you were able to resolve this issue on site 1e1bfc09-eda6-4764-bf6a-63a643627e05, is that accurate?
I am seeing failed builds for site e1b1ed31-6b28-4473-835a-f99717561741, but they seem to be due to a different issue.