VSCode - Export failure

[Drac-Zhang]

Describe the Bug with repro steps

1. Create a Logic App Consumption as per provided workflow definition, it need to have "Azure Storage Table - Get Entities" action and a "Foreach" action. The Foreach action's input need to be entities list.

2. Use VS Code Export tool to export the workflow, then we will experience the exception:

The export package URL experienced an unknown problem.

Encountered internal server error. The tracking Id is '0700895d-db2b-4755-b1e1-f8375cbcdf59'.

What type of Logic App Is this happening in?

Standard (VSCode)

Are you using Preview Designer or GA Designer

Generally Available

Workflow JSON

{
    "definition": {
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
        "actions": {
            "For_each": {
                "actions": {},
                "foreach": "@body('Get_entities_(V2)')?['value']",
                "runAfter": {
                    "Get_entities_(V2)": [
                        "Succeeded"
                    ]
                },
                "type": "Foreach"
            },
            "Get_entities_(V2)": {
                "inputs": {
                    "host": {
                        "connection": {
                            "name": "@parameters('$connections')['azuretables']['connectionId']"
                        }
                    },
                    "method": "get",
                    "path": "/v2/storageAccounts/@{encodeURIComponent(encodeURIComponent('AccountNameFromSettings'))}/tables/@{encodeURIComponent('testtb')}/entities"
                },
                "runAfter": {},
                "type": "ApiConnection"
            }
        },
        "contentVersion": "1.0.0.0",
        "outputs": {},
        "parameters": {
            "$connections": {
                "defaultValue": {},
                "type": "Object"
            }
        },
        "triggers": {
            "manual": {
                "inputs": {
                    "schema": {}
                },
                "kind": "Http",
                "type": "Request"
            }
        }
    },
    "parameters": {
        "$connections": {
            "value": {
            }
        }
    }
}

Screenshots or Videos

No response

Browser

Edge

Additional context

No response

AB#24578330

[ccastrotrejo]

Hi @Drac-Zhang sorry for not replying earlier. Is this issue still happening?

[ccastrotrejo]

Closing the issue as there was no answer, if this keeps happening I will be opening the issue and take a further look on it.

[amshivraj]

Can anyone please tell, what might be the solution for this? I have been getting this error too. THe logic app has child flows and also blob and d365 related connectors..

[ccastrotrejo]

Hi @amshivraj thanks for letting us know I will take another look at this issue

[sonasona2024]

Hi, I am also getting the same error like above, I am trying to export the logic app consumption to Standard using VS code, the error is not very descriptive.

[ccastrotrejo]

Hi @sonasona2024 thank you so much for sharing the screenshot. I am working to get the right exception/error from the tracking id and provide a fix or workaround to export it correctly

[sonasona2024]

@ccastrotrejo did you get chance to look into the issue. My Logic app is using message queue, connection to SQL SERVER, smtp and also connection to sharepoint to check the file, but in the microsoft page I do not see any components which I am using, is it the reason that export is failing?

[ccastrotrejo]

Hi @sonasona2024 yes I was able to trace back the issue and there is an ongoing issue with the message queue while exporting it. I will reach out to once this gets solved or the BE engineers reach out to me. I would say that not showing the actions types in the list should matter. There is a step in the export experience which we review/validate the operations and connections and we makes sure those are exportable.

[sonasona2024]

@ccastrotrejo Thank you very much, please let me know if there is any updates.

[BiancaOliveiraGit]

@ccastrotrejo Is there an update on the issue with exporting the message queue connector?

[ccastrotrejo]

Hi @BiancaOliveiraGit there isn't an update yet. I just revisited the issue with our backend team, and they will triage it.

[anshmathur]

@ccastrotrejo We are facing the export failure for some more logic apps that include Azure Queue and SMTP connector. Tracking ids below for reference.

[BiancaOliveiraGit]

@anshmathur @ccastrotrejo @sonasona2024 I found a workaround to allow the queue connector to migrate. I discovered that the error with the queue connector was only happening on V1 of the queue connector.

Workaround: In the portal, in the ‘Logic app code view’ amend all queue trigger and actions amend all “path” properties. the main difference is the prefix /v2/storageAccounts/@{encodeURIComponent(encodeURIComponent('AccountNameFromSettings'))}

example:     "path": "/v2/storageAccounts/@{encodeURIComponent(encodeURIComponent('AccountNameFromSettings'))}/queues/@{encodeURIComponent(concat(parameters('env'),parameters('active_queue_prefix'),parameters('queue_contactus')))}/message_trigger"   Save the workflow & now will be able to migrate using the VS Code extension tools.      

[anshmathur]

@BiancaOliveiraGit unfortunately the workaround doesn't work in my case. Appended /v2/storageAccounts/ export still failing. The export package URL experienced an unknown problem. Encountered internal server error. The tracking Id is 'b26b4e88-d467-4f7f-a9e1-e834c72e9756'.

I guess, the only "truly manual" workaround is to delete/replace trigger/action with another dummy action (that can be exported) and replace it back after export.

[BiancaOliveiraGit]

@anshmathur my only suggestion is to ensure that you also have 'queues' apart of that append string. if that still doesn't work then yes "replace with another action/trigger" to spot the difference

[anshmathur]

Thanks @BiancaOliveiraGit. I was a bit ignorant when I tried it initially, I didn't look at the entire "path" format. Yes your suggestion on path is spot on, it resolved the issue with export.

/v2/storageAccounts/<StorageAccount Name>/queues/<Queue Name>/message*

[ccastrotrejo]

Hi all, can anyone verify if this issue is still going on?

[ccastrotrejo]

I will close this issue, if this keeps happening I will take a further look and re open it

[TimoKarhu]

Hi yes, I have it happening on "Exec SQL Query V2" which was not healthy on the source lga. If possible, the error message on the exporter might be more informative. Perhaps not in your hands. Now that we know it, one should always check for connectors in case of "exception" in the exporter.

Thanks!