# Managing Dynamic Engine environments in Talend Management Console

Manage your Dynamic Engine environments from the Dynamic Engine Environments tab in the Environments page.

These environments can be used with Dynamic Engines only and can be assigned to a single Dynamic Engine at a time.

You must have the Environment Administrator (ID: TMC\_ENVIRONMENT\_MANAGEMENT) role to access the Dynamic Engine Environments tab.

## Dynamic Engine Environment Statuses

| Status | Description |
| --- | --- |
| Not assigned | Your Dynamic Engine environment has been created but not associated<br>to a Dynamic Engine.<br><br>This environment can already be used in task or<br>plan configuration but nothing can be actually run. |
| Setup required | Your administrator has started to assign this environment to a<br>Dynamic Engine, and so a Helm values file has been generated.<br><br>This Dynamic<br>Engine environment is waiting for this Helm values file to be installed<br>on the Kubernetes cluster, so as to be eventually assigned to a<br>Dynamic Engine. |
| Ready | After the successful Helm installation, your<br>Dynamic Engine environment has been associated to a Dynamic Engine and<br>can be used to run tasks and plans. |
| Not ready | An error occurred during the Helm installation while installing<br>or connecting at least one service. Alternatively, the installation or<br>connection was successful but later disconnected.<br><br>The status of this<br>Dynamic Engine environment becomes Not ready.<br><br>Information noteTip: Specific to Data Service and Route tasks:<br><br>When a<br>Dynamic Engine environment transitions to Not ready,<br>Data Services or Routes in Running status<br>(shown as STARTING\_FLOW\_EXECUTION in logs and<br>executing in API responses) will have their<br>task sub-state updated to TASK\_INACTIVE in the<br>execution history, while the parent task status remains<br>unchanged. Once the environment returns to<br>Ready status, the tasks automatically<br>synchronize and the sub-state returns to<br>TASK\_ACTIVE. You can view the task sub-state<br>in execution history logs and API responses.<br><br>For further<br>information on deployment statuses of Data Services and Routes,<br>see [Deployment statuses](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/managing-data-services-and-routes-in-dynamic-engine-environments-in-tmc). |

### In this section

* [Viewing the list of Dynamic Engine environments](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/viewing-list-of-dynamic-engine-environments)
* [Viewing and editing the details of a Dynamic Engine environment](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/viewing-and-editing-details-of-dynamic-engine-environment)
* [Unassigning an environment from a Dynamic Engine](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/unassigning-environment-from-dynamic-engine)
* [Deleting a Dynamic Engine environment](https://help.qlik.com/talend/en-US/dynamic-engine-configuration-guide/Cloud/deleting-dynamic-engine-environment)