Azure
Custom: Unable to fetch custom connectors operations
Describe the Bug with repro steps
- Create a custom connector with sentiment.json file.
- Create a LogicApp in the same subscription and same location as your customConnector created. (I have created both in West central US location)
- Go to Edit blade for your Logic App
- You should see your custom connector and its operations in the recommendation card when filter runtime with custom as trigger.
Expected: Created custom connectors in the same subscription and same region should be found when we filter runtime with custom.
Actual: Unable to fetch custom connectors operations
What type of Logic App Is this happening in?
Consumption (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
No response
Screenshots or Videos
https://github.com/user-attachments/assets/8df8ee3e-d102-480a-9bb1-56dad7125c85
Browser
Edge
Additional context
Version: 0.2022.1.764
@vgouth - Please send me an email with the network logs captured before you open the designer and until you observe the issue.. Faster would be keep the repro in the logic app and do not delete it, and give me access so i can look at it
Issue still repro in the latest build.
Version: 2.41007.1.5
@preetriti1 Given you contributor access to logic app custom connector and logic app.
This is fixed in 2.41007.1.9 and above, just verified in staging that this is working.
@rllyy97 @vgouth @Eric-B-Wu @preetriti1 : We still experience this issue. This is issue is much more serious from today since the legacy designer is not available anymore ! When is deployment of fix planned?
Hi @simenums, can you try two things for me, they might help unblock you.
I'm currently seeing that the browse (no search input) is not working as expected in all scenarios for custom connectors, but if I search I am able to see my custom actions/triggers.
Please also try unchecking the Action Type filters so none are selected. This also made the custom actions/triggers appear for me in search.
We are looking into what caused this and will update you when we have an ETA on a fix!
@rllyy97 Issue repro in latest test pass. Unable to fetch connectors when we search/ filter with custom runtime. Able to fetch custom connectors in actions while filtering with custom runtime and when we search. But for trigger case we are not able to fetch the custom connectors. Version : : 2.41028.1.2
@rllyy97 Issue repro in latest test pass. Unable to fetch connectors as triggers when we search/ filter with custom runtime. Able to fetch custom connectors in actions while filtering with custom runtime and also when we search without filtering with custom runtime.
Version : : 2.41028.1.6
@vgouth Can you try to repro in staging again? Staging is running 2.41028.1.12 and I'm not able to reproduce this issue.
Browse shows the connector:
And searching for the action also shows results:
@rllyy97. In the last staging request with version 0.2022.1.796, I was unable to create logic apps custom connectors. Currently, I am still facing the same issue. I will re-evaluate this in the next staging version. If the issue is resolved, I will close it with a comment.
@rllyy97 Issue repro in latest staging test pass.Unable to fetch connectors as triggers when we search/ filter with custom runtime. Able to fetch custom connectors in actions while filtering with custom runtime and also when we search without filtering with custom runtime. Version: 2.50107.1.3
@rllyy97 Issue repro in latest staging test pass.Unable to fetch connectors as triggers when we search with custom connector name/ filter with custom runtime. Able to fetch custom connectors in actions while filtering with custom runtime and also when we search with custom connector name without filtering with custom runtime.
Version: 2.50203.1.2
@rllyy97 Issue repro in latest staging test pass,Unable to fetch connectors as triggers when we search with custom connector name/ filter with custom runtime. Able to fetch custom connectors in actions while filtering with custom runtime and also when we search with custom connector name without filtering with custom runtime. Version: 2.50324.1.5
@rllyy97 Issue repro in latest canary test pass, Unable to fetch connectors as triggers when we search with custom connector name/ filter with custom runtime. Able to fetch custom connectors in actions while filtering with custom runtime and also when we search with custom connector name without filtering with custom runtime.
Version: 2.0.20250408.2
@rllyy97 Issue repro in latest staging test pass. Unable to fetch connectors as triggers when we search/ filter with custom runtime. Able to fetch custom connectors in actions while filtering with custom runtime and also when we search without filtering with custom runtime.
Version: 2.50425.1.3
@rllyy97 Issue repro in latest canary test pass. Unable to fetch connectors as triggers when we search/ filter with custom runtime. Able to fetch custom connectors in actions while filtering with custom runtime and also when we search without filtering with custom runtime.
Version: 2.0.20250512.2
@rllyy97
Issue repro in latest staging test pass. Unable to fetch connectors as triggers when we search/ filter with custom runtime.
Able to fetch custom connectors in actions while filtering with custom runtime and also when we search without filtering with custom runtime.
Version: 2.50522.1.10
@rllyy97 Issue repro in latest staging test pass. Unable to fetch connectors as triggers when we search/ filter with custom runtime. Able to fetch custom connectors in actions while filtering with custom runtime and also when we search without filtering with custom runtime. Stage Version: 2.50616.1.1
@rllyy97
Looks like this issue is fixed in the latest stage test pass. Now, I was able to fetch both custom connector operators in triggers and actions. Closing this issue for now.
Version: 2.50808.1.1