Unexpected Error working with new environment

Feature(s) impacted

Can not set a new environment as Production, Can not push to a new environment, Can not sync from a new environment, Error deleting new environment, error changing to the new environment.

Observed behavior

Interaction with a new environment does not work. There are 3 environments, DEV, UAT, PRD.
UAT was automatically set as production, PRD (new environment) is supposed to be the new production environment, but fails every time you try to do something with it, even trying to select it, returning 500 error for every action.

Expected behavior

Expecting it will let you interact as with any other environment.

Failure Logs


  • Project name: Enixa
  • Team name: Enixa / Project ID: 78929
  • Environment name: PRD / ENV
  • Agent type & version: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/ Safari/537.36

Hello @J-Wolff,

Thanks for reaching out and sorry for the inconvenience!

That’s pretty clear on our side that something is not right with this environment PRD.
Now, we’ll try to fix it asap and also we’ll try to understand how it could end up in this situation.

Could you please tell how did you create this environment?
From the UI? The CLI?



Thanks for your prompt answer!
It was done through the UI.

As a side note, a similar issue but no so critical is happening with another environment named “Production [temp]”, where it won’t let you set it as production, and will trigger another error 500.

Thanks for your help!


Hi @J-Wolff,

Thanks for your answer!

Ok, we’ve detected a bug. It concerns the environment creation when using a name that was used for another environment creation in the past (even if this environment was deleted or renamed after)…
So we’ll open a bug report and this would be fixed asap.

Meanwhile, let’s try to resolve your issue now.

  • Are you able to delete your PRD environment? If not, do you authorise us to delete it?
  • And in order to have your next production environment, could you please try to create a new environment with a totally random name (to be sure you’ve never named a former environment like that) and do the operations we wanted to do. And please don’t rename it yet, we’ll tell you when you can.

Thanks a lot and very sorry for the inconvenience.


The new environment is ready and seems to be working fine, I was able to delete the old one as well.

The name of the new environment is ENV4F86

Thanks again!

1 Like


Thanks a lot for keeping us posted!

That’s good news. Sorry again for the trouble.
We’ll let you know as soon as possible when there is no risk to rename it.



After more thinking with the team, you can actually rename your environment as you want as of now.
In fact, the only trouble is when creating an environment with a name that was used for creating another one. No issue with renaming.

Let me know!
Thanks again for your report.

1 Like

Guys thanks heaps for your help.

I can confirm that all the environments are working fine, even after renaming them to the name that initially caused the error.


1 Like

Hello @J-Wolff ,
I am working on the patch. Are you still using the “new_production” environment?