# Dev Environment Stuck on "Your project is being configured."

**URL:** https://community.forestadmin.com/t/dev-environment-stuck-on-your-project-is-being-configured/7020
**Category:** Help me!
**Created:** [February 1, 2024, 4:32pm UTC](https://community.forestadmin.com/t/dev-environment-stuck-on-your-project-is-being-configured/7020 "2024-02-01T16:32:32Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![yeti182](https://avatars.discourse-cdn.com/v4/letter/y/858c86/32.png) [@yeti182](https://community.forestadmin.com/u/yeti182)
#### Post date: [February 1, 2024, 4:32pm UTC](https://community.forestadmin.com/t/dev-environment-stuck-on-your-project-is-being-configured/7020/1 "2024-02-01T16:32:32Z")

</div>

Hi -

We recently updated our forest-cli version and upon creating a new forest branch, our development environment is now stuck on “Your project is being configured.” I’ve tried deleting the .forestadmin-schema to see if that would help, but it doesn’t.

Could you look into this, please?

Thanks!

---

<div class="post-metadata">

### Author: ![GuillaumeGautreau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/guillaumegautreau/32/557_2.png) [@GuillaumeGautreau](https://community.forestadmin.com/u/GuillaumeGautreau)
#### Post date: [February 1, 2024, 4:35pm UTC](https://community.forestadmin.com/t/dev-environment-stuck-on-your-project-is-being-configured/7020/2 "2024-02-01T16:35:08Z")

</div>

Hello @yeti182,

Could you please share with us the exact command that you launched?

Also, could you please share the required info when creating a post in the community?

Thanks

```javascript
<!-- ⚠️ This is a template you must use to report issues. ⚠️ -->
<!-- You can also drag images, videos and include pre-formatted text. -->

## Feature(s) impacted
<!-- Please describe in this mandatory section the feature(s) that will be discussed in this topic. -->

## Observed behavior
<!-- Please describe in this mandatory section the current behavior you observe. -->

## Expected behavior
<!-- Please describe in this mandatory section the behavior you are expecting. -->

## Failure Logs

<!-- In this optional section, please include any relevant log snippets if necessary. -->
<!-- Or remove this section if left empty. -->

## Context

<!-- Please provide in this **mandatory section** , the relevant information about your configuration: -->
- Project name: ...
- Team name: ...
- Environment name: ...
- Agent (forest package) name & version: ...
- Database type: ...
- Recent changes made on your end if any: ... 

```

---

<div class="post-metadata">

### Author: ![yeti182](https://avatars.discourse-cdn.com/v4/letter/y/858c86/32.png) [@yeti182](https://community.forestadmin.com/u/yeti182)
#### Post date: [February 1, 2024, 4:36pm UTC](https://community.forestadmin.com/t/dev-environment-stuck-on-your-project-is-being-configured/7020/3 "2024-02-01T16:36:38Z")

</div>

Hi @GuillaumeGautreau - happy to, but I’ll send the private details in a DM, if that’s okay.

Command to launch is the one we’ve always used: `nodemon ./server.js`

## Features impacted

Ability to access dev environment

## Observed behavior

When loading our development environment, it is stuck on “Your Project is Being Configured”

 ![Screenshot 2024-02-01 at 11.05.14 AM](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/4/4b27e2e9c44ce106a446d324b637ad764f8c1065.png)

## Expected behavior

It should load…

## Failure Logs

None

## Context

DM’d

---

<div class="post-metadata">

### Author: ![yeti182](https://avatars.discourse-cdn.com/v4/letter/y/858c86/32.png) [@yeti182](https://community.forestadmin.com/u/yeti182)
#### Post date: [February 1, 2024, 8:37pm UTC](https://community.forestadmin.com/t/dev-environment-stuck-on-your-project-is-being-configured/7020/4 "2024-02-01T20:37:16Z")

</div>

It looks like the start of our issue coincided with a Forest API degradation. I’ve tried logging out/logging in as well as a different browser, but the issue persists. Could you please check to see if something happened related to this outage: [Users cannot execute variou... | ForestAdmin](https://status.forestadmin.com/incident/320935)

We’re unable to complete any development due to this issue - any help would be appreciated!

---

<div class="post-metadata">

### Author: ![GuillaumeGautreau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/guillaumegautreau/32/557_2.png) [@GuillaumeGautreau](https://community.forestadmin.com/u/GuillaumeGautreau)
#### Post date: [February 2, 2024, 7:53am UTC](https://community.forestadmin.com/t/dev-environment-stuck-on-your-project-is-being-configured/7020/5 "2024-02-02T07:53:37Z")

</div>

Hello @yeti182,

Thanks for pointing out the recent issue we had. I’m still investigating if it affected your particular environment.

In the meantime, I re-launched a processing on your project that should normally allow you to access it. Could you please make a try?

If it’s not the case, could you please open the developer tools in your browser and report any error from the console?

Thanks

---

<div class="post-metadata">

### Author: ![GuillaumeGautreau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/guillaumegautreau/32/557_2.png) [@GuillaumeGautreau](https://community.forestadmin.com/u/GuillaumeGautreau)
#### Post date: [February 2, 2024, 8:21am UTC](https://community.forestadmin.com/t/dev-environment-stuck-on-your-project-is-being-configured/7020/7 "2024-02-02T08:21:18Z")

</div>

My investigations show that there is still a problem with your development environment.

We are continuing investigations to understand the impacts of yesterday’s incident on your environment and to fix the issue.

I’ll keep you posted when I have news.

---

<div class="post-metadata">

### Author: ![GuillaumeGautreau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/guillaumegautreau/32/557_2.png) [@GuillaumeGautreau](https://community.forestadmin.com/u/GuillaumeGautreau)
#### Post date: [February 2, 2024, 9:26am UTC](https://community.forestadmin.com/t/dev-environment-stuck-on-your-project-is-being-configured/7020/8 "2024-02-02T09:26:09Z")

</div>

It seems that your schema contain invalid declarations of some enum fields:

```javascript
          {
            "type": "Enum",
            "enums": null,
            "field": "currentSpeechEngine",
            "inverseOf": null,
            "isVirtual": true,
            "reference": null,
            "isReadOnly": false,
            "isRequired": false,
            "isSortable": false,
            "integration": null,
            "validations": [],
            "defaultValue": null,
            "isFilterable": false,
            "isPrimaryKey": false
          },

```

And

```javascript
          {
            "type": "Enum",
            "enums": null,
            "field": "Subscription Plan ID",
            "widget": null,
            "position": 2,
            "reference": null,
            "isReadOnly": true,
            "isRequired": true,
            "description": "This is automatically populated based on the selected subscription plan.",
            "defaultValue": null
          },

```

```javascript
          {
            "hook": "onSubPlanChange",
            "type": "Enum",
            "enums": null,
            "field": "Subscription Plan Name",
            "widget": null,
            "position": 1,
            "reference": null,
            "isRequired": true,
            "description": "This is the type and price for new the subsription.",
            "defaultValue": null
          }

```

In all of these cases, it’s not valid to have both `"type": "Enum"` and `"enums": null`. The value of `enums` **must be an array**.

I think the problem comes only from the first one, that declares an enum in the collection `Users`.

We’re working on correctly handling this kind of invalid declaration, but in the meantime can you try to fix the declaration on your side?

---

<div class="post-metadata">

### Author: ![GuillaumeGautreau](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/guillaumegautreau/32/557_2.png) [@GuillaumeGautreau](https://community.forestadmin.com/u/GuillaumeGautreau)
#### Post date: [February 2, 2024, 11:07am UTC](https://community.forestadmin.com/t/dev-environment-stuck-on-your-project-is-being-configured/7020/9 "2024-02-02T11:07:45Z")

</div>

Small update: we managed this invalid value case on our side, and your project should be fully usable now.

Thank you for reaching us about your issue.

---

<div class="post-metadata">

### Author: ![yeti182](https://avatars.discourse-cdn.com/v4/letter/y/858c86/32.png) [@yeti182](https://community.forestadmin.com/u/yeti182)
#### Post date: [February 2, 2024, 1:03pm UTC](https://community.forestadmin.com/t/dev-environment-stuck-on-your-project-is-being-configured/7020/10 "2024-02-02T13:03:29Z")

</div>

Hi @GuillaumeGautreau -

Thanks for the update, and we are able to use our dev environment now. Looks like the null `enums` field was due to a misspelling of `enums` as `enunms` in our config. The issue must not have cropped up until we made a new branch. Thanks for getting us up and running again!