Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logic App Std - Azure Devops connector API connection Edit/Save gives an error: Test connection failed. Error 'Key 'Token' not found in connection profile.' #6207

Open
ZoltanK-MSFT opened this issue Dec 3, 2024 · 4 comments
Assignees
Labels
Portal This issue resides in Portal

Comments

@ZoltanK-MSFT
Copy link

ZoltanK-MSFT commented Dec 3, 2024

Describe the Bug with repro steps

This issue is reproducible for Customer and also for me.

  1. In the Resource Group, select the already existing DevOps (visualstudioteamservices) API connection.
  2. Go to General -> Edit API connection -> Reauthorize -> Save
  3. the error appears: Test connection failed. Error 'Key 'Token' not found in connection profile.'

Same functionality works fine in Logic App designer.

Impact:

Customer deploy logic app via devops, and need to set the password that cannot be set at devops release level.

This functionality is also used by when the associated password expires or changes.

Image

What type of Logic App Is this happening in?

Standard (Portal)

Which operating system are you using?

Windows

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

Screenshots or Videos

Image

Browser

Chrome

Additional context

No response

@hartra344 hartra344 added the Portal This issue resides in Portal label Dec 4, 2024
@DanielleCogs
Copy link
Contributor

Able to reproduce with my own connection

@rllyy97
Copy link
Contributor

rllyy97 commented Dec 17, 2024

@ZoltanK-MSFT Do you know when this issue started occurring? And are you seeing this behavior on any other connector besides the DevOps connector you mentioned?
I looked around at some other connectors and could only reproduce it on this one.
I also loaded up a fairly old version of the portal extension and still saw this issue. We haven't changed anything that would be causing this in over a year, so if this is somewhat new behavior for this customer then I think this might be coming from something related to the connector.

@rllyy97
Copy link
Contributor

rllyy97 commented Dec 17, 2024

@Eric-B-Wu and I investigated further and we found the issue! We're working on a fix and will update you here once we have it working.

@Eric-B-Wu Eric-B-Wu self-assigned this Dec 18, 2024
@Eric-B-Wu
Copy link
Contributor

We have a fix on the portal repository which we will deploy onto staging once deployment freeze is unpaused

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Portal This issue resides in Portal
Projects
None yet
Development

No branches or pull requests

5 participants