I am currently encountering an issue while attempting to import a flow that has been exported as a package (zip) from tenant A to tenant B.
I have frequently utilized this method in the past to effortlessly copy flows to another tenant, following these steps:
1. Export the flow on Tenant A and generate/save the resulting ZIP fiel
___________________________
2. On the new tenant B: I choose "Import Package (Legacy)
___________________________
3. I upload the Package Zip File, correct the connection for SharePoint and confirm with "Import"
___________________________
4. I encounter this message but it was always manageabe as I can proceed by clicking on "Save as a new flow"
Typically, I would be redirected to the flow editor, allowing me to swiftly adjust corresponding SharePoint lists, connections, etc. Afterwards, I simply saved the flow, and it was successfully copied to the new tenant B.
However, I am currently encountering an error message that did not occur in the past:
I've attempted various flows with entirely new tenants and connections, but I consistently encounter this error message now. I've even retried scenarios from previous instances where I know this approach worked successfully. This error never surfaced in the past, and based on my frequent use of this approach, it seems to have arisen around October or November.
___________________________
Debugging approaches:
- I delved into the Package's ZIP file and modified the flow's name within the "definition" JSON file, for instance, to "A."
- Despite making these adjustments and repeating the steps, I still receive a similar error message:
It is certain that the name is not being retrieved from another source, as I have now changed the name to "A," and the error message reflects the new name I selected.
It appears that when clicking on "Save as a new flow," Power Automate automatically generates a new flow with the name "draft_[flow name from definition.json]," which is causing issues.
I suspect that this might be a bug.
___________________________
Note:
I am already aware that an alternative solution involves building a solution and then importing the entire package. However, for this particular use case, setting up such a solution is not resource-efficient.
From my limited perspective, I hypothesize that the "_" within the flow name is causing an issue, aligning with the error message. Nonetheless, users have no control over the automatically generated flow draft name.
