Feature(s) impacted
Default environment
Observed behavior
For some reason, one of our development remote environments got set up as the default environment of the project. We have no idea how this happened or how to revert it but it causes an error for everyone of our users trying to access the project since it first tries to load this env which they don’t have access to.
Expected behavior
I believe the production environment should be the default one.
Failure Logs
Context
- Project name:
- Team name: …
- Environment name: …
- Agent (forest package) name & version: …
- Database type: …
- Recent changes made on your end if any: …
Hello @Eyal_Hakim,
Can you please fill in the required information about your project:
Project name:
Team name: …
Environment name: …
Agent (forest package) name & version: …
Database type: …
Recent changes made on your end if any: …
I’m unable to help you without this information.
Hi @GuillaumeGautreau unfortunately I prefer not to fill in our internal project information on a public space, this was one point of feedback I gave your team when they decided to stop offering support via email and only offering the community.
I am more than happy to send you this information privately via email.
In your project settings:
- Select the “Environments” tab
- Select your production environment
- Click on the button “Set as production” on the bottom of the page.
Does it fix your issue?
The button is disabled with the message above it saying: “This environment is your production environment.”
Hey @Eyal_Hakim
Your issue is similar to this one, and we will keep you updated about the resolution there.
Sorry for the inconvenience.
Hey @Eyal_Hakim,
The issue should be fixed on your end, as visible on the thread I previously mentionned.
Let me know if you are still encountering an issue, and sorry for the inconvenience otherwise.