[BUG] Azure Dev Ops

[pipedream-component-development]

App

Azure Dev Ops

Summary:

Cannot Assign event type string returns two empty parameters as options and nothing is selectable

Details:

Cannot Assign event type in my trigger string. It returns two empty parameters as options and nothing is selectable. All my previous pipelines are also broken because of this as I am unable to trigger any triggers

Screenshots:

[mohamedlotfy95]

HI
Check Permissions:
Ensure that the account you are using has the necessary permissions to access and configure triggers in Azure DevOps. You might need to be an administrator or have specific permissions to manage service hooks.

Refresh Connection:
Try refreshing the connection to Azure DevOps. You can do this by:

Clicking on the "Refresh field" button as shown in the screenshot.
Re-authenticating your Azure DevOps account in the configuration settings.
Clear Cache:
Sometimes, clearing the browser cache can resolve issues related to UI elements not loading correctly. Clear your browser cache and try again.

Check for Updates:
Ensure that you are using the latest version of the tool or extension you are working with. There might be updates or patches that address this issue.

Review Logs:
Check the logs for any error messages or warnings that might give you more insight into why the Event Type options are not loading. This can be done in the Azure DevOps portal or the tool you are using.

Network Issues:
Ensure that there are no network issues or firewall settings that might be blocking the connection to Azure DevOps.

Contact Support:
If the issue persists, consider reaching out to Azure DevOps support for assistance. Provide them with the details and screenshots of the issue for a quicker resolution.

[vunguyenhung]

I can reproduce this issue.

To component dev, please use the Microsoft account component-dev@pipedreamdevelopers.onmicrosoft.com

[michelle0927]

@vunguyenhung Are you still able to reproduce this? I tested with the account component-dev@pipedreamdevelopers.onmicrosoft.com and am not seeing the error.