Question

Your team ships a managed solution containing an environment variable named 'ApiBaseUrl' that has a default value pointing to the development endpoint. In the test environment, an administrator previously set a current value pointing to the test endpoint. After you import an updated version of the managed solution (which changes the default value to a new development endpoint), users report that the flows are still calling the old test endpoint. What is the cause of this behavior?

Accepted Answer

The environment variable's current value in the test environment takes precedence over the default value, and imports do not overwrite an existing current value.

Answer

Managed solution imports always reset environment variable current values to the default value, so the flow is misconfigured elsewhere.

Answer

Environment variables cannot be used inside cloud flows, so the URL must be hardcoded in the flow action.

Answer

The default value from the newest solution layer overrides the current value, so the flow should be calling the new development endpoint.