question

hichamveo avatar image
0 Votes"
hichamveo asked hichamveo commented

Logic App standard problem saving Azure blob connector

I'm facing a strange issue with one of my clients where I'm unable to savle my workflow after adding Azure blob connector "Get blob content using path (V2)". The connection is established and can browse blob and select my file, but when I save , "Save" button becomes activated and lose my changes if I close the workflow, no error is raised. With my own subscription it works fine. someone have an idea? thanks in advance for the help.

azure-logic-apps
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@hichamveo Please repro the issue and share the session ID from azure portal (ctrl + alt + d). Please also share the gif/screenshoot reproducing the issue.
Do you see any error in Notifications when you click on save button?

0 Votes 0 ·

No error on from notifications blade.
Session ID: 2e9389c6e112419498822e93330b85d0

when I save , the button "Save" is reactivated":

129816-image.png



NB: when I use built-in connector (not Azure one), it works fine and can save my workflow

0 Votes 0 ·
image.png (46.4 KiB)

1 Answer

MayankBargali-MSFT avatar image
0 Votes"
MayankBargali-MSFT answered hichamveo commented

@hichamveo Thanks for sharing the details.
I have looked into the backend logs and found that the workflow failed to save as there was issue with API connection access policy name. When you are using any action that uses the connection internally it creates the API connection access policy name with the naming convention as yourresourcegroupname-workflowname-randomguidID and currently this API connection access policy name has the limit of 80 character.
AFAIK I don't see this name can be set from the workflow and I have reached out to my team to confirm the same. I have also passed the feedback to the portal UI team if the portal experience can be enhanced with the right error message if possible in this case. Once I have update from my team I will update this thread.

Currently the workaround is to have your resourcegroupname and workflowname name combining less than 42 character. As two character are used for - and 36 character for random guid.

Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thhank you @MayankBargali-MSFT for your hgelp, your solution has fixed my problem. Please share the feedback if an enhance is released

0 Votes 0 ·