Logic App Designer - Unable to initialize operation...

[WilMorland]

Describe the Bug with repro steps

This issue has occurred following an attempt to deploy a logic app workflow using Azure Powershell. A definition file is submitted. A manually created logic app via UI, with the same JSON definition schema works as expected.

The application uses API connections to Office365 and Service Bus, both of which are successfully connected.

Opening one of the nodes starts an endless load, so no further information is available there for debugging.

This appears very similar to #5977.

The below schema has had real, valid email addresses swapped out for placeholders.

What type of Logic App Is this happening in?

Consumption (Portal)

Which operating system are you using?

Windows

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

Yes

Workflow JSON

{
    "definition": {
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
        "contentVersion": "1.0.0.0",
        "triggers": {
            "When_a_message_is_received_in_a_topic_subscription_(auto-complete)": {
                "recurrence": {
                    "interval": 1,
                    "frequency": "Minute"
                },
                "evaluatedRecurrence": {
                    "interval": 1,
                    "frequency": "Minute"
                },
                "type": "ApiConnection",
                "inputs": {
                    "host": {
                        "connection": {
                            "name": "/subscriptions/{redacted-subscriptionId}/resourceGroups/s1-lpremediation-rg-dev/providers/Microsoft.Web/connections/s1-lpremediation-etl-servicebus-connection-dev"
                        }
                    },
                    "method": "get",
                    "path": "/@{encodeURIComponent(encodeURIComponent('s1-lpremediation-etl-notification-topic-dev'))}/subscriptions/@{encodeURIComponent('s1-lpremediation-etl-topic-subscription-dev')}/messages/head",
                    "queries": {
                        "subscriptionType": "Main"
                    }
                }
            }
        },
        "actions": {
            "Send_an_email_(V2)_person2": {
                "runAfter": {},
                "type": "ApiConnection",
                "inputs": {
                    "host": {
                        "connection": {
                            "name": "s1-lpremediation-etl-email-connection-dev"
                        }
                    },
                    "method": "post",
                    "body": {
                        "To": "[email protected]",
                        "Subject": "Error Notification",
                        "Body": "<p class=\"editor-paragraph\">@{base64ToString(triggerBody()?['ContentData'])}</p>",
                        "Importance": "Normal"
                    },
                    "path": "/v2/Mail"
                }
            },
            "Send_an_email_(V2)_person1": {
                "runAfter": {},
                "type": "ApiConnection",
                "inputs": {
                    "host": {
                        "connection": {
                            "name": "s1-lpremediation-etl-email-connection-dev"
                        }
                    },
                    "method": "post",
                    "body": {
                        "To": "[email protected]",
                        "Subject": "Error Notification",
                        "Body": "<p class=\"editor-paragraph\">@{base64ToString(triggerBody()?['ContentData'])}</p>",
                        "Importance": "Normal"
                    },
                    "path": "/v2/Mail"
                }
            }
        },
        "outputs": {},
        "parameters": {
            "$connections": {
                "type": "Object",
                "defaultValue": {}
            }
        }
    },
    "parameters": {
        "$connections": {
            "value": {
                "servicebus": {
                    "id": "/subscriptions/{redacted-subscriptionId}/providers/Microsoft.Web/locations/uksouth/managedApis/servicebus",
                    "connectionId": "/subscriptions/{redacted-subscriptionId}/resourceGroups/s1-lpremediation-rg-dev/providers/Microsoft.Web/connections/s1-lpremediation-etl-servicebus-connection-dev",
                    "connectionName": "s1-lpremediation-etl-servicebus-connection-dev"
                },
                "office365": {
                    "id": "/subscriptions/{redacted-subscriptionId}/providers/Microsoft.Web/locations/uksouth/managedApis/office365",
                    "connectionId": "/subscriptions/{redacted-subscriptionId}/resourceGroups/s1-lpremediation-rg-dev/providers/Microsoft.Web/connections/s1-lpremediation-etl-email-connection-dev",
                    "connectionName": "s1-lpremediation-etl-email-connection-dev"
                }
            }
        }
    }
}

Screenshots or Videos

No response

Browser

Chrome, app deployed via Azure automation runbook using Azure Powershell

Additional context

No response

[ccastrotrejo]

Hi @WilMorland thanks for raising this issue. If manually creating the Logic App via UI, with the same JSON definition schema works as expected, I would check if the Azure Powershell script is the one causing the issue.

• By manually creating the LA in the UI, do you mean copy/pasting the JSON in the codeview? or doing it via the designer?
• Is the powershell script also deploying the connections?
• Can you check if the environment variables in the Logic App are the same when using the powershell script and the UI?

[hartra344]

UX is generally likely doing the correct thing and there's likely an issue with deployment so I'm closing this issue for now. @WilMorland @ccastrotrejo gave some good tips above to some good ways to try troubleshooting. THere are generally multiple steps to setting up a logic app with connections such as deploying the connections, creationg hte proper ACLS between the logic app and connections, etc. The designer generally handles all of this behind the scenes when it's in control but it needs all of this to be there to properly render.