Issue exporting solution with cloud flow from DEV environment

[Luis_Alex_Chin]

Hi everybody!

I work in a corporate environment; in the organization's tenant, there is the default environment, the DEV environment, the QA environment, and the PROD environment. Currently, I use the DEV environment to create flows and applications. The issue is that if I create a solution that does not contain Power Automate flows, I can export it without any issues from this DEV environment. However, as soon as I add a flow (whether I create it within the solution or externally, whether it's manual, automatic, or scheduled), just adding a flow to the solution generates this error:

System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Workflow export: FAILURE, workflow id {327518d8-5067-ed11-9562-000d3ae8ca44} category ModernFlow name dumyflow (Fault Detail is equal to Exception details: 
ErrorCode: 0x80040216
Message: Workflow export: FAILURE, workflow id {327518d8-5067-ed11-9562-000d3ae8ca44} category ModernFlow name dumyflow
TimeStamp: 2022-11-18T15:02:18.8587138Z
--).

The curious thing is that if I do the exact same thing in the default environment, no matter what type of flow and connections I add, I can export it without any problems. Can someone help me with this? I have been searching forums for 4 days, and those with a similar error have not received satisfactory answers. I have tried with very simple Power Automate flows that practically don't connect to anything (just initializing a variable or something), and the export still doesn't work in the DEV environment.

I'd really appreciate if somebody could help me!

[DarmonGill]

Hi,

Here are some steps you can take to troubleshoot and potentially resolve the problem:

1. Check Permissions: Ensure that the account you're using to export the solution has the necessary privileges to access and export flows in the DEV environment. Verify that the account has the required security roles and permissions.

2. Review Flow Dependencies: Sometimes, flows may have dependencies on specific connectors, custom connectors, or resources that might not be available or properly configured in the DEV environment. Review the connectors and dependencies used in your flows and ensure they're correctly set up in DEV.

3. Flow Configuration and Settings: Verify the configurations of the flows you're attempting to include in the solution. Ensure that all necessary details are properly filled out, and there are no errors or missing information within the flow configurations.

4. Check for Environment-specific Settings: There might be certain environment-specific settings or configurations affecting flow exports in the DEV environment. Compare the settings between the DEV and default environments, looking for any discrepancies that could cause issues during export.

5. Review Environment Differences: Since you mentioned that the same export works in the default environment but not in DEV, check for any environmental differences between the two. This could include versioning, environment-specific settings, connector configurations, etc.

Br,

Gill

[Luis_Alex_Chin]

Hello Mr. Gill. Thank you very much for your advice, I'm going to ask the administrator to check if there are differences between the environments and their configuration. I had reviewed the issue of permits and it was fine. I will let you know what we found, thank you very much.

[TheRealPascal]

@Luis_Alex_Chin Hi, have you found any solution to this? The same problem is currently affecting our entire DEV environment.