It appears that the function core tools would only work with the built in triggers in local environments. The Azure triggers might only work in the Azure runtime environment.
Apologies for the inconvenience caused.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi there,
I tried running a logic app workflow with azure functions core tools with the servicebus trigger "When_a_message_is_received_in_a_queue_(auto-complete)" and ran into some problems.
There are no exceptions at all, just a debug message that says: "Workflow '<workflowname>' does not have a mapped function trigger, skipping function metadata injection." The workflow won't be loaded afterwards.
I guess this trigger is not supported yet? Is there a list of supported triggers or is there anything I could have done wrong?
Just for testing, I tried the same with a http trigger and with the servicebus trigger "When messages are available in a queue". Everything was executed as expected.
I am using the newest version of Azure Function Core Tools and the newest version of azurite and so on.
In portal this runs as expected, so I don't see where I could be wrong.
This is the workflow I tried to run:
{
"definition": {
"$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
"actions": {},
"contentVersion": "1.0.0.0",
"outputs": {},
"triggers": {
"When_a_message_is_received_in_a_queue_(auto-complete)": {
"inputs": {
"host": {
"connection": {
"referenceName": "serviceBus"
}
},
"method": "get",
"path": "/@{encodeURIComponent(encodeURIComponent('queuename'))}/messages/head",
"queries": {
"queueType": "Main"
}
},
"recurrence": {
"frequency": "Second",
"interval": 15
},
"type": "ApiConnection"
}
}
},
"kind": "Stateful"
}
Really would appreciate any help/information about this.
It appears that the function core tools would only work with the built in triggers in local environments. The Azure triggers might only work in the Azure runtime environment.
Apologies for the inconvenience caused.