This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 46%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGL%3C/text%3E%3C/svg%3E)
I am using custom connectors to make API requests and since today when I open them and want to edit I get a white screen where normally the parameters of the connector should be.
We tried in different ressource groups and subscriptions but everywhere the same. We can still create and delete the connectors but not editing.
We also tried with different users and browsers (also incognito).
Does anybody have a solution for this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 59%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
@GAERTNER Lukas Thanks for reaching out. I am able to reproduce this issue at my end will check with Product group team and get back to you.
@JananiRamesh-MSFT I see that I still have the issue. Do you already know when it will be solved?
@GAERTNER Lukas Thanks for getting back, Product group is actively working on it will update you as soon as i hear back from them.
apologize for the inconvenience caused by the issue. Feel free to add a comment if any questions.
@JananiRamesh-MSFT thank you for the info. Is this a global issue? I am wondering, that I dont see other people complaining about it.
We have the same problem from Italy. Support say me to use or command az logic or HTTP API but for the first there is not a specific command for update custom connector and for the last I cannot find documentation.
How we can overcome this problem?
We have the same problem from Italy. How can we overcome this problem?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(272, 36%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKG%3C/text%3E%3C/svg%3E)
Same issue here
@GAERTNER Lukas Thanks for getting back, this seems to be a global issue and i see many customers reported the same. Product group works in PST hours will check for an ETA and will update you.
we appreciate your patience on this topic!
@JananiRamesh-MSFT this blocks the finalization of a project business is waiting for. They chose Azure because of its reliability, now I have to explain them why this is not given at the moment.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(3.2, 72%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ETC%3C/text%3E%3C/svg%3E)
Any update on this? The issue is almost a week old
@JananiRamesh-MSFT I see that the behaviour is still there.
Could the product group team make any progress in the last day?
Any update on this? At least a workaround? This issue is open since last week.
@GAERTNER Lukas can try this to update your logic apps custom connector:
@JananiRamesh-MSFT thank you for the link. But I have too many connectors to recreate everyone.
@JananiRamesh-MSFT this is still not fixed, do you have a plan on when it will be working again?
Hi everyone, using the stackoverflow link provided in another comment here I've been able to prepare an ARM template, and deploy it pretty easily. This can be done directly from the Logic apps custom connector, using the Deploy function in the Export tab.
In the next step is possible to edit the template, in my case I've added the swagger node with the definition, removed apiDefinitions and wsdlDefinition and the deploy updated the swagger for the connector.
@JananiRamesh-MSFT now in my logic apps there is some strange behavior, this sign "[" is replaced by "~2" and the API calls are not working properly anymore. Has this something to do with the recent fix?
@GAERTNER Lukas Thanks for your patience! The issue is resolved, and the fix has been deployed across the impacted regions please verify and let me know incase of further queries, I would be happy to assist you.
Please accept as Yes if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.
@JananiRamesh-MSFT thank you, it looks good.
What was the reason for the error?
@JananiRamesh-MSFT since this bug was solved another one is appearing, now when I use my custom connectors in my logic apps this sign "[" is recognized as "~2" and they can not be used anymore in parameters.
In custom connectors where I cant use a body instead of parameters, this makes them impossible to use. Is this a bug?
Do you know a workaround?
Hi GAERTNER Lukas Thanks for getting back, this is a different question to the initial thread question, and I recommend you post as a new question in Q&A so that it would also help others in the community. We would gladly assist you in new thread
Hi @JananiRamesh-MSFT I made this [https://learn.microsoft.com/en-us/answers/questions/2118557/custom-connector-bug-wrong-interpretation-(](https://learn.microsoft.com/en-us/answers/questions/2118557/custom-connector-bug-wrong-interpretation-()
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 54%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFN%3C/text%3E%3C/svg%3E)
Any update on this matter? Would be nice to have an ETA