I have been playing around with Logic App Standard a bit and came across a gotcha which I am sure ill fall into again so saving for my notes.

The scenario was as follows:

  • I build a logic app / workflow in visual studio code
  • I deploy the logic app to Azure and the deployment is successful
  • The logic app looks ok in Azure and I can see its reporting as healthy
  • The workflow looks ok in the designer
  • When I test the workflow i am getting an error triggering the workflow
  • The workflow opens ok in the designer and nothing seems out of place

I had originally assumed something about how im calling the workflow was wrong so I wanted to check the trigger via the management API. I ran the below query via API playground

/subscriptions/92357fca-2391-4501-b98a-6a93589ba4c9/resourceGroups/Blog-Dataverse-Sync/providers/Microsoft.Web/sites/mikes-logic-app/hostruntime/runtime/webhooks/workflow/api/management/workflows?api-version=2018-11-01

I get back the below result and I can see that there is a problem with the workflow.

[
  {
    "name": "dataverse-sync",
    "definition_href": "https://ms-la-dataverse-cosmos-sync-dev.azurewebsites.net/admin/vfs/site/wwwroot/dataverse-sync/workflow.json",
    "href": "https://ms-la-dataverse-cosmos-sync-dev.azurewebsites.net/runtime/webhooks/workflow/api/management/workflows/dataverse-sync",
    "kind": "Stateless",
    "triggers": {
      "manual": {
        "type": "Request",
        "kind": "Http"
      }
    },
    "isDisabled": false,
    "health": {
      "state": "Unhealthy",
      "errorMessage": {
        "error": {
          "code": "InvalidTemplate",
          "message": "The template validation failed: 'The action(s) 'Compose_-_Dataverse_Item' referenced by 'inputs' in action 'Compose_-_Cosmos_Properties' are not defined in the template.'."
        }
      }
    }
  }
]

I went into the designer and tried to change the workflow and save it and I get the same error flagging up.

The problem was that in the action that has the error I have an expression which references another action and I have a typo in the action name.

For some reason the vs code deployment doesnt pick this up so the lesson learned is if you get a problem running a trigger the healthy on the portal seems to refer to the run history rather than the workflow being runable.

 

Buy Me A Coffee