microsoft / coe-starter-kit

Other
739 stars 216 forks source link

[ALM Accelerator - BUG]: Issue with Switching Environments in ALM Accelerator for Power Platform #8688

Open Kebo-ard opened 1 month ago

Kebo-ard commented 1 month ago

Describe the issue

I have the ALM Accelerator installed in my "DEV" environment using the March 2024 versions. After the installation, I created a new environment named "DEMO". When I switch environments in the "ALM Accelerator for Power Platform" canvas app, it works fine for the "DEV" environment and other environments that existed prior to the installation of the Center of Excellence - ALM Accelerator. However, when switching to the newly created "DEMO" environment, I encounter the following issues:

  1. In the canvas app, I receive the following error message:

GetEnvironmentSolutions.Run failed: { "error": { "code": 502, "source": "asia-001.azure-apim.net", "clientRequestId": "bb768a1e-dc91-4517-9bac-ed8f5691eace", "message": "BadGateway", "innerError": { "error": { "code": "NoResponse", "message": "The server did not receive a response from an upstream server. Request tracking id '08584798652328512292853398515CU45'." } } } }

image

  1. The flow named "GetEnvironmentSolutions" fails when I switch the environment in the canvas app to "DEMO". The flow provides the following error message:

No Organization is matching the given dataset: _

image

Expected Behavior

Switching to the newly created "DEMO" environment should not result in any errors, and the "GetEnvironmentSolutions" flow should run successfully.

What component are you experiencing the issue with?

ALM Accelerator Canvas App

What solution version are you using?

1.0.20240305.1

Steps To Reproduce

  1. Install the ALM Accelerator in the "DEV" environment using the March 2024 versions.
  2. Create a new environment named "DEMO".
  3. Open the "ALM Accelerator for Power Platform" canvas app.
  4. Switch the environment to the newly created "DEMO" environment.
  5. Observe the error message in the canvas app.
  6. Check the "GetEnvironmentSolutions" flow and observe the failure details.

Anything else?

No response

AB#3870

mikefactorial commented 1 month ago

@Kebo-ard it might help to know if there is anything distinct about the new DEMO environment that might be causing issues compared to the environments that are working? For example, does the demo enivronment include a Dataverse Database, are your permissions different in the DEMO environment compared to the environments that are working? Is the environment in a different Region? Also, it can be helpful to troubleshoot if you look at a successful run of the flow vs the failed run of the flow. Is there anything distinctive in the failed call vs the successful call that might point to the reason for the failure.

Kebo-ard commented 1 month ago

Thank you for your help with the issue. Interestingly, after a few days, the error seems to have resolved itself. I didn't make any changes, but it appears that everything is now working fine. I even created a new environment and selected it in the ALM Accelerator for Power Platform, and there were no errors.

Thanks again for your support!