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

[jeanpaulsmit]

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

[azure-boards[bot]]

❌ There was a problem linking to Azure Boards work item(s):

• 25485707

Please check the IDs and try again using the AB# syntax. Learn more

[azure-boards[bot]]

❌ There was a problem linking to Azure Boards work item(s):

• 25485707

Please check the IDs and try again using the AB# syntax. Learn more

[azure-boards[bot]]

❌ There was a problem linking to Azure Boards work item(s):

• 25485707

Please check the IDs and try again using the AB# syntax. Learn more

[azure-boards[bot]]

❌ There was a problem linking to Azure Boards work item(s):

• 25485707

Please check the IDs and try again using the AB# syntax. Learn more

[azure-boards[bot]]

❌ There was a problem linking to Azure Boards work item(s):

• 25485707

Please check the IDs and try again using the AB# syntax. Learn more

[azure-boards[bot]]

❌ There was a problem linking to Azure Boards work item(s):

• 25485707

Please check the IDs and try again using the AB# syntax. Learn more

[azure-boards[bot]]

❌ There was a problem linking to Azure Boards work item(s):

• 25485707

Please check the IDs and try again using the AB# syntax. Learn more

[azure-boards[bot]]

❌ There was a problem linking to Azure Boards work item(s):

• 25485707

Please check the IDs and try again using the AB# syntax. Learn more

[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?