Create connection to ASB peek-lock trigger fails with 'Failed to create connection: Unknown error'

[jeanpaulsmit]

trafficstars

Describe the Bug with repro steps

1. Create new Logic App in VSCode
2. Create Service bus "When messages are available in a queue (peek-lock)" trigger
3. Specify name, type 'connectionstring' and populate that field
4. Error shows up

What type of Logic App Is this happening in?

Standard (VSCode)

Are you using new designer or old designer

New Designer

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

Yes

Workflow JSON

No response

Screenshots or Videos

No response

Browser

n/a

Additional context

The error is not providing any information about the why, so not really helpful.

Actually, it reminds me of the infamous Sharepoint error 'an error occurred'.

I found out later that localauth on ASB was disabled, so it made sense it couldn't connect.

However, it would be much more helpful when the error would not say 'Unknown error' but a more descriptive one.

Maybe the VSCode extension receives some kind of 401, which could at least guide the dev in that direction.

AB#25485707

[rllyy97]

Hi @jeanpaulsmit, we've added a decent bit of improved error checking and propagation since you reported this issue, can you check to see if this is resolved for you or if we need to take another look at it?

[github-actions[bot]]

We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed.

[jeanpaulsmit]

@rllyy97 thanks for getting back about this topic. I just tested and there is no difference in response for me:

I'm using v3.0.3 of the extension, which I believe is the latest at the moment.

[github-actions[bot]]

We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed.

[github-actions[bot]]

This issue has been closed because the information requested wasn't provided within 7 days.

[Eric-B-Wu]

@rllyy97 did we do investigation on this one or should it be reopened?

[rllyy97]

I did not investigate, reopening

[piyushpaliwal]

I am hitting the same issue but with "Send a message" action. Is there any workaround that we could potentially try while the team is working on fixing the issue? Maybe create the connection in portal and use that?

[Banchio]

I have same issue (screenshot below). Expectation here, by using Managed Identity, would be to use currently logged-on user in vs code while debugging locally and use Managed Identity while running in Logic App (similar to what happen when using DefaultAzureCredentials in dotnet). Is this correct?

[Banchio]

I was able to go ahead by creating the connection manually in Azure logic apps and then pasting it in the connections.json file. My hope on the managed identity does not work unfortunately.

[MrRosendahl]

@rllyy97 The bug/feature?, in my case, is really that actions are always forced to choose a topic from a dropdown, which is populated through the connection. But a connection might not be authorized to access to all topics/queues.

For security reasons we want to lock down our apps in the service bus as much as possible, and we therefore use connectionstring directly from a specific topic. Currently these service bus actions only work when a connectionstring is from the service bus shared access policies and not from a shared access policy on a topic or a queue... might be by design, but please consider security and the possibility to specify a topic (without the need for a dropdown).

Below is my earlier text before I realized that the issue was with the dropdown

I got the same error using Connection String, "Failed to create connection: Unknown error" when creating an In-app action "Complete the message in a topic subscription" (I also tried to create Service bus In.-app trigger for reading messages).

I used (the primary) "Connection String" for both In-app and non In-app.

The non In-app works. So, at least for me, this is a Service bus In-app error.

In-app

Non In-app

[rllyy97]

Hi all, @ccastrotrejo and I will take a look at this issue soon, sorry you've had to wait so long. We'll check it out and let you know what we find soon, thank you for the helpful information you've added!