Neon branching error in vercel build
Not sure where to find logs or debugging info for this integration
22 Replies
flat-fuchsia•2y ago
Hey! Sorry to hear that you're running into an issue. What is the region of your Neon project?
multiple-amethystOP•2y ago
US East Northern Virginia
This is showing up on my staging branch
flat-fuchsia•2y ago
Hmm, if you retry your Preview deployment, will the issue still persist?
multiple-amethystOP•2y ago
Yes the issue persists after redeployment
flat-fuchsia•2y ago
Hmm, do you mind sharing with me your Vercel deployment ID? You can find it in the URL of the page you shared in your screenshot
multiple-amethystOP•2y ago
Hey @Mahmoud, here is the ID 5W2mrtqek7JwcQR24SRJuYWfYDog
flat-fuchsia•2y ago
Hmm so it seems that there was an issue with setting the environment variable on the preview deployment but we're unable to reproduce the issue. Do you mind removing the integration, adding it again and seeing if the deployment works?
multiple-amethystOP•17mo ago
Yes, it seems to have been spamming builds on vercel overnight and now vercel is blocking deployments on my account
flat-fuchsia•17mo ago
it seems to have been spamming builds on vercel overnightI don't think the integration has a retry logic, but I'll check internally
now vercel is blocking deployments on my accountto make sure I understand correctly, right now you can't create Preview Deployments? What type of error are you getting
multiple-amethystOP•17mo ago
I don't think the integration was retrying, it was that the error was blocking depoyment success. Maybe vercel was autoretrying? I'm not sure exactly what was going on with that.
multiple-amethystOP•17mo ago
@Mahmoud Here is a breakdown of what we've been seeing https://gist.github.com/meandavejustice/02afeb260da60ee195eec0490d92c272
Gist
Neon vercel integration issues
Neon vercel integration issues. GitHub Gist: instantly share code, notes, and snippets.
flat-fuchsia•17mo ago
I'll share this with the team. Thank you for providing all the details
ambitious-aqua•17mo ago
Getting a similar issue. Getting the same "Neon branching · Status not available" and my Vercel builds are getting cancelled, then a new build is requested, then its cancelled, and in an endless cycle
Any updates on this so far?
My project is located in US West (Oregon)
ambitious-aqua•17mo ago
Okay, I think I may have found the cause. I usually unchecked
DATABASE_URL when setting up the Vercel integration as we use the other envs below. I did this twice when re-connecting and got the same re-building endless loop issue. However reading this message: https://discord.com/channels/1176467419317940276/1242355078883704872/1243299112678326414, I tried re-connecting the Vercel integration one more time with the DATABASE_URL env included this time. Triggering a re-deploy on Vercel worked.
So there might be a bug where Neon doesn't check the other envs, only the DATABASE_URL env, even if I disabled it
multiple-amethystOP•17mo ago
@Mahmoud Have you heard anything back from the team?
I can share more details if they have any specific asks
flat-fuchsia•17mo ago
Unfortunately we don't know how to reproduce the issue :/
When setting up the integration, are there any settings you're tweaking or are you sticking to the defaults?
multiple-amethystOP•17mo ago
I was just using database_url and database_url_unpooled. The only difference seemed to be that I have a staging branch
So basically, all of our pull requests are against the staging branch. It seemed like that is what the integration was having issues with. I have environment variables that are set for staging manually. [Preview on Staging] is what it would look like (staging is the git branch)
Those are pointed to my neon staging db
WIll try adding again this evening and report back
🤞
multiple-amethystOP•17mo ago
Okay just added back and confirmed. The preview branches build fine. The errors are caused on all of my staging builds by neon integration. A possible fix would be adding a setting for neon to ignore certain branches you set. Having a staging branch is really common so I'd be suprised if more users aren't affected by this
multiple-amethystOP•17mo ago
cc/ @Mahmoud ^
flat-fuchsia•17mo ago
The good news is that this is on our roadmap. I'll let you know once it ships
I'm glad you were able to pinpoint the cause of the issue
I also really appreciate the through reporting. It's been super helpful
multiple-amethystOP•17mo ago
Awesome thank you!
@Mahmoud Can you ping me whenever this feature lands?
flat-fuchsia•17mo ago
Will do 🫡