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)
Recently this bug (https://learn.microsoft.com/en-us/answers/questions/2105547/azure-logic-app-custom-connector-not-editable) was solved, but immediately after another one appeared.
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?
An Azure service that automates the access and use of data across clouds without writing code.
![](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. Looking into this issue will get back to you shortly.
@GAERTNER Lukas Thanks for your patience! We apologize for the inconvenience caused by the issue. I had a discussion internally and could see few customers reported the same issue and our product group team is investigation it currently, will update you as soon as i hear back from them.
@GAERTNER Lukas Just checking to see if you have chance to see previous response and helped. Please let us know if you have further queries.
@JananiRamesh-MSFT you wrote in your previous comment you will provide a private portal link, which I didnt get. So I am still waiting for this.
@GAERTNER Lukas Thanks for getting back, private azure portal url https://ms.portal.azure.com/?Microsoft_Azure_EMA=carlos
The fix is not fully deployed to prod, ETA for it will be mid-December or mid-January
Do let me know incase of further queries, I would be happy to assist you.
@GAERTNER Lukas Do you have a chance to check on my below answer? Please let us know if you have more questions and please kindly accept the answer to support the community. Thanks a lot.
@GAERTNER Lukas Just checking to see if you have chance to see previous response and helped. Please let us know if you have further query or issue remains.
@JananiRamesh-MSFT do you know when this bug is finally fixed?
The manual workaround is not working anymore, when I update the logic app action in code view this jumps back to ~2 again after saving.
@JananiRamesh-MSFT do you already know when this will be fixed? The workaround is not working at my side.
@GAERTNER Lukas Thanks for your patience! PG team identified the bug and manual workaround to this bug is after the creation of the workflow in designer view, you can go to code view and update the schema replacing the "~2" with "[" manually and save it.
here is the private azure portal url with the fix https://ms.portal.azure.com/?Microsoft_Azure_EMA=carlos
The fix is not fully deployed to prod, ETA for it will be mid-December or mid-January
please try and do let me know incase of further queries, I would be happy to assist you.
If you found the answer to your question helpful, please take a moment to mark it as Yes for others to benefit from your experience. Or simply add a comment tagging me and would be happy to answer your questions.