Follow up on NODE_ENV no longer set in runtime

Feedback
1

I wanted to follow up on the issue I opened last week: NODE_ENV no longer set in runtime

First, thank you for addressing it promptly. It does feel like it needs some sort of follow up from the Vercel team though. This issue caused a significant outage on one of our production applications, and we need to make sure this does not happen again.

The main concern our team has is that we are using Vercel in a way that is not officially supported or tested. Beyond that, we would like to understand what actually happened and have reassurance that steps have been taken to prevent this from happening in the future.

Thanks!

1 Like
2

Hi, @beerlington!

We identified that the issue was related to a new feature currently in development. The team addressed it earlier this week, and we’ve implemented additional tests to prevent similar issues in the future.

Thanks for your patience :pray:

3

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