Can someone tell me how I can contact Netlify support re my raised ticket 1072831 apparently this has been escalated to the engineers. But I have had no confirmation of this even after asking for it. And the general support emails look like they are AI generated. So it appears I am relying on AI to pass this on.
This is business critical now as we can not deploy to production and have been unable to do so for 6 days. We are a charity and we are a paying customer on the pro option. This really isn’t acceptable.
If you are reading this and you are part of the Netlify team please can you jump on this urgently.
Hey @georgemillard, thank you for getting in touch, and sincere apologies for the hassle. I see we’ve followed up internally, and we’ll continue to work in that thread to ensure we get this issue resolved as soon as possible.
Hi Marcus
Can you please get this nudged to the top of the list. It’s been over a week and we can not push anything to production. The email prior to the last one where they said they would escalate to the engineering team told me to change some config but that was already tried and we have the ENV set up for:
GATSBY_EXCLUDE_DATASTORE_FROM_BUNDLE=true
anyway and always have for at least 3 years since we had to move from Gatsby cloud to Netlify. They also said they were escalating this a week ago, but I have had nothing to confirm this happened. And given it was almost certainly
an AI response I have my doubts if it was even pushed to engineering.
It also seems co-incidental that Netlify made a major upgrade to their functions 2 days before the builds suddenly started failing. So I’m assuming this maybe something to do with however the ssr function is now being packaged.
When testing locally via the Netlify CLI the bundle only comes out at 63mb much smaller than the 250mb limit.
The deploy also worked and the site built and worked fine as well. So it seems to be the bundling step on Netlify that is the issue here.
Any assistance you can give to get this moved on quickly would be appreciated as this is now business critical.
Kind regards
Hey @georgemillard, thanks again for following up here, and I really appreciate your feedback regarding the communication while we worked to resolve this issue.
I can confirm both that it was a human who escalated this issue and that the fix was indeed shipped by our Frameworks team. It looks like the internal thread is resolved as well, but please don’t hesitate to reach back out if there’s anything else we can assist with.