Environment to Staging is disabled with no info message

[Max]

1. My goal:

• to set the environment to staging

2. Issue:

• The staging env is disabled and when I hover my mouse on it, it does not show any message in the black round box as shown in the 4) additional info

3. Steps I've taken to troubleshoot:

• I checked that the app that seems to have an issue uses the resources that is multi-env configured.
• When I change the value of the localStorage key appEnvironment from "production" to "staging", it works.

4. Additional info: (Cloud or Self-hosted, Screenshots)

• Cloud
• Team plan
• It worked fine until yesterday

1) not showing any message in the black box

---

2) this multi page app uses the resource that needs multi-env configuration

---

2-1)

2-2)

3) We use Team plan

---

4) when the app is loaded, there is this error message showing in the devtool console

runtime.DVchXwbq.umd.js:69 error in computeTemplateStringDependencies  .value  SyntaxError: Unexpected token . (at runtime.DVchXwbq.umd.js:47:14026)
    at e.raise (runtime.DVchXwbq.umd.js:47:14026)
    at e.unexpected (runtime.DVchXwbq.umd.js:48:130)
    at pp$3.parseExprAtom (runtime.DVchXwbq.umd.js:42:38185)
    at pp$3.parseExprSubscripts (runtime.DVchXwbq.umd.js:42:33381)
    at pp$3.parseMaybeUnary (runtime.DVchXwbq.umd.js:42:32943)
    at pp$3.parseExprOps (runtime.DVchXwbq.umd.js:42:31344)
    at pp$3.parseMaybeConditional (runtime.DVchXwbq.umd.js:42:30987)
    at pp$3.parseMaybeAssign (runtime.DVchXwbq.umd.js:42:30387)
    at pp$3.parseParenAndDistinguishExpression (runtime.DVchXwbq.umd.js:42:40304)
    at pp$3.parseExprAtom (runtime.DVchXwbq.umd.js:42:37468)

[Jack_T]

Hi @Max,

Apologies for the issue. Normally an environment will only be displayed but greyed out with (disabled) when the resource is missing the corresponding environment.

Can you check to see if there are any other queries in the app that are using resources that may only have prod and not staging environments enabled?

Sometimes a new query can sneak through without both environments. My second guess if this is the only query/resource in the app would be to try deleting the staging env set up and creating it again.

That is very odd that it was working fine until a day before your post. I can ask around internally to see if there might be a change to the code base that could have caused this.