UnresolvableHostName: LogicApps Microsoft Teams connector

Question

UnresolvableHostName: LogicApps Microsoft Teams connector

Lopez Alonso, Luis 186

Hi,

I've a Standard LogicApp, VNET integrated.

I've created a workflow (same error between statefull and stateless) to react to a MS Teams message in a specified channel. For this, I've used Microsoft Teams connection with a valid API Connection.

When I save the workflow, automatically on Trigger Runs, appears errors. Looking in my AppInsights I can see the following error (Id's are changed due to privacy):

Workflow trigger ends. flowName='MY_NAME', triggerName='When_a_new_channel_message_is_added', flowId='LONG ID', flowSequenceId='LONG ID', status='Failed', statusCode='UnresolvableHostName', error='{"code":"UnresolvableHostName","message":"Http request failed with status code 'HostNotFound' and status message: 'No such host is known.'."}', extensionVersion='1.3.7.0', siteName='MY_STANDARD_LOGIC_APP', slotName='Production', durationInMilliseconds='21', flowRunSequenceId='', inputsContentSize='225', outputsContentSize='-1', clientTrackingId='LONG ID', properties='{"$schema":"2016-06-01","startTime":"2023-02-28T11:28:38.4872026Z","endTime":"2023-02-28T11:28:38.5153043Z","status":"Failed","code":"UnresolvableHostName","fired":false,"resource":{"workflowId":"LONG ID","workflowName":"MY_NAME","runId":"LONG ID","triggerName":"When_a_new_channel_message_is_added"},"correlation":{"clientTrackingId":"LONG ID"},"error":{"code":"UnresolvableHostName","message":"Http request failed with status code 'HostNotFound' and status message: 'No such host is known.'."},"api":{}}', triggerType='ApiConnection', flowScaleUnit='cu00', triggerKind='', sourceTriggerHistoryName='', failureCause='', overrideUsageConfigurationName='', hostName='MY_STANDARD_LOGIC_APP.azurewebsites.net', activityId='LONG ID'.

My workflow is quite simple, as we are now in POC stage (I only want to be able to react to a MS Teams message): User's image

What's wrong with this logicApp workflow?

Ton of thanks for your support

Regards,

Luis

David Broggy 6,291 Reputation points MVP Volunteer Moderator

2023-03-01T07:35:54.0266667+00:00

Hi Luis,

It looks to me like you're not assigning the right variable to your logic app.

'No such host is known.'."}'

A trick I use to validate my variables is to add an email operator and in the body of the email print out all of your variables.

Good luck.
Lopez Alonso, Luis 186 Reputation points

2023-03-01T08:50:07.2333333+00:00

Thanks for your response @David Broggy but the error is on connectors trigger (no parameters are set, only the API Connection and TeamsId/ChannelId)

1 answer

Your answer

David Broggy 6,291 Reputation points MVP Volunteer Moderator

2023-03-01T07:35:54.0266667+00:00

Hi Luis,

It looks to me like you're not assigning the right variable to your logic app.

'No such host is known.'."}'

A trick I use to validate my variables is to add an email operator and in the body of the email print out all of your variables.

Good luck.
Lopez Alonso, Luis 186 Reputation points

2023-03-01T08:50:07.2333333+00:00

Thanks for your response @David Broggy but the error is on connectors trigger (no parameters are set, only the API Connection and TeamsId/ChannelId)

Answer 1

MayankBargali-MSFT 70,936 Moderator

@Lopez Alonso, Luis Thanks for reaching out. Can you please confirm if there are no restrictions/disabled Allow public access on the Inbound traffic to your standard logic app? In case if you have enabled the Access Restrictions on your standard logic app then the azure connector will not be able to communicate with your logic app.

As you are using the team's connector so the internally there would be webhook that would be used to trigger your workflow by the connector and as Team Connector is Azure connector so azure connector can only access it over internet. In case if you have blocked the access then your workflow will not be triggered.

Azure Team Connector (inbound webhook callbacks) --> standard logic app workflow (through team trigger)

In the above case you need to make sure that you are adding the rule to allow the connector IP address if you have disable "Allow public access" to the inbound traffic.

Please accept as "Yes" if the answer is helpful so that it can help others in the community. If you need any help/clarification/concerns/follow up questions, then please click on "Add Comment" on my answer and provide more details.

Lopez Alonso, Luis 186 Reputation points

2023-03-01T09:01:43.22+00:00

Thanks for your response @MayankBargali-MSFT

Actually no inbound traffic access restrictions are configured for Standard LogicApp

Any additional thoughts?

Ton of thanks for your support :)

Regards

Luis
MayankBargali-MSFT 70,936 Reputation points Moderator

2023-03-01T09:14:35.2466667+00:00

@Lopez Alonso, Luis Can you retry to configure the trigger again with reauthentication/creating the new connection again to see if it helps you to resolve the issue. Please confirm the region where you have deployed your logic app, workflow state type (stateful/stateless). Can you please reconfirm if you are able to see the trigger history when you add a test channel to make sure that the logic app is trigger but there could be different issue and share whether you see (along with error message) the successful, failed or skipped on your trigger history when you perform the test operation.

Lopez Alonso, Luis 186

@MayankBargali-MSFT I've configured trigger again (i've deleted the workflows and API Connections, and created again)

I've both workflows (statefull/stateless) and error is the same on trigger history. I've deployed Standard Logic App in WestEurope.

After adding the trigger in the workflow (statefull/stateless), Trigger History looks like this:

User's image

If I access the first trace, looks like:

User's image

In the link there are no helpfull information, only channelId....

On AppInsights, I can see following error:

Workflow trigger ends. flowName='TEAMS_STATELESS', triggerName='When_a_new_channel_message_is_added', flowId='LONG ID', flowSequenceId='LONG ID', status='Failed', statusCode='UnresolvableHostName', error='{"code":"UnresolvableHostName","message":"Http request failed with status code 'HostNotFound' and status message: 'No such host is known.'."}', extensionVersion='1.3.7.0', siteName='MY_LOGIC_APP_NAME', slotName='Production', durationInMilliseconds='9', flowRunSequenceId='', inputsContentSize='225', outputsContentSize='-1', clientTrackingId='LONG ID', properties='{"$schema":"2016-06-01","startTime":"2023-03-01T16:42:40.7474384Z","endTime":"2023-03-01T16:42:40.7642069Z","status":"Failed","code":"UnresolvableHostName","fired":false,"resource":{"workflowId":"LONG ID","workflowName":"TEAMS_STATELESS","runId":"LONG ID","triggerName":"When_a_new_channel_message_is_added"},"correlation":{"clientTrackingId":"LONG ID"},"error":{"code":"UnresolvableHostName","message":"Http request failed with status code 'HostNotFound' and status message: 'No such host is known.'."},"api":{}}', triggerType='ApiConnection', flowScaleUnit='cu00', triggerKind='', sourceTriggerHistoryName='', failureCause='', overrideUsageConfigurationName='', hostName='MY_LOGIC_APP_NAME', activityId='LONG ID'.

Thanks!!!

Regards

Luis

Lopez Alonso, Luis 186 Reputation points

2023-03-03T07:48:47.2366667+00:00

Hi @MayankBargali-MSFT any thoughts about last post?

Ton of thanks for your patience and support.

Kind regards

Luis
MayankBargali-MSFT 70,936 Reputation points Moderator

2023-03-03T08:11:55.4966667+00:00

@Lopez Alonso, Luis Apology. Looks like I missed your last comment. I wish to engage with you offline for a closer look and provide a quick and specialized assistance, please send an email with subject line “Attn:Mayank” to AzCommunity[at]Microsoft[dot]com referencing this thread along with your availability in UTC so I can schedule the call to review it.
Lopez Alonso, Luis 186 Reputation points

2023-03-07T09:17:52.98+00:00

@MayankBargali-MSFT Hi Mayank, email was sent. Waiting your reply :)

Thanks a ton for your support
Regards!
Luis

Share via

UnresolvableHostName: LogicApps Microsoft Teams connector

1 answer

Your answer