AEM solution for environment creation failures in Cloud Manager
Environment creation in Cloud Manager can fail when another environment operation is already running, required product profiles are missing, or access and pipeline configuration are incomplete. Checking active environment operations, confirming Adobe Admin Console product profiles, and reviewing related pipeline status often resolves the issue.
Description description
Environment
Adobe Experience Manager as a Cloud Service, including Adobe Experience Manager Forms as a Cloud Service when forms-related product profiles are required.
Issue/Symptoms
Environment creation in Cloud Manager can fail before provisioning completes, and the interface may show messages such as Environment creation failed or Non-production pipeline creation failed.
- The environment creation workflow stops unexpectedly or does not complete.
- The new environment does not move into a normal provisioning state.
- A related non-production pipeline does not complete successfully.
- You can confirm the issue by checking the program’s environments list for an operation that does not progress as expected, verifying that no other environment creation is already in progress, and confirming that the required Adobe Admin Console product profiles are available.
- If the environment includes forms capabilities, confirm that the required forms-related service profiles are present in Adobe Admin Console.
Resolution resolution
Try the following steps to solve the issue:
- Open Cloud Manager and review the program’s environments list. If another environment creation or deletion is still running, wait until that operation finishes, and then try again. Expected result: the list shows completed or idle operations, and a new environment request can start normally.
- In Adobe Admin Console, confirm that the required Cloud Manager and AEM product profiles exist and that the appropriate users are assigned to them. If the environment includes forms capabilities, verify that the required forms-related service profiles are also available. Expected result: the needed product profiles are present and assigned correctly.
- Sign out of Cloud Manager, sign in again, and retry the environment creation. Expected result: the request moves from pending to provisioning instead of failing immediately.
- Review the program’s non-production pipeline configuration in Cloud Manager. If a related pipeline exists, confirm that it is available and not in a failed or incomplete state, and rerun it if appropriate. Expected result: the pipeline completes normally or shows a clear error that you can address.
- If the retry still fails, collect customer-safe verification details such as the failure timestamp, the program ID, screenshots of the environments list, and any visible pipeline error information from Cloud Manager.
If the following symptoms occur and the troubleshooting steps produce the following results, submit a ticket to Adobe Support:
- The environment continues to fail after no other environment operation is running.
- The required product profiles exist, are assigned correctly, and a fresh sign-in does not change the result.
- The related pipeline remains unavailable, fails again, or shows an error that you cannot resolve from Cloud Manager.
Submit a ticket and include the failure timestamp, program ID, screenshots, and any visible Cloud Manager error details.