Azure / LogicAppsUX

https://learn.microsoft.com/azure/logic-apps
MIT License
75 stars 81 forks source link

Send_an_email_(V2) action fails with attachment, when added using new logic app designer #5133

Closed sagnik17 closed 1 month ago

sagnik17 commented 3 months ago

Describe the Bug with repro steps

When dynamic content for attachment added using new designer, the content type didn't added base64 conversion by default, as below

"Attachments": [ { "ContentBytes": "@{body('Get_blob_content_(V2)')}", "Name": "@body('Parse_JSON')?['ExportFileName']" } ],

While in case of old designer, it was added by default, as below

Attachments": [ { "ContentBytes": "@{base64(body('Get_blob_content_(V2)'))}", "Name": "@body('Parse_JSON')?['ExportFileName']" } ],

Repro Steps

  1. Create Logic App.
  2. Use new designer to develop the workflow.
  3. Select Get_blob_content_(V2) action.
  4. Select attachments and select the dynamic content from previous step.

What type of Logic App Is this happening in?

Consumption (Portal)

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

When dynamic content for attachment added using new designer, the content type didn't added base64 conversion by default, as below

"Attachments": [ { "ContentBytes": "@{body('Get_blob_content_(V2)')}", "Name": "@body('Parse_JSON')?['ExportFileName']" } ],

While in case of old designer, it was added by default, as below

Attachments": [ { "ContentBytes": "@{base64(body('Get_blob_content_(V2)'))}", "Name": "@body('Parse_JSON')?['ExportFileName']" } ],

Browser

Chrome & Edge

Additional context

No response

Eric-B-Wu commented 3 months ago

@sagnik17 thanks for reporting this issue, I'll take a look at why this is happening. This may be a regression caused because Power Automate (which is built off our designer) doesn't cast these tokens to base64 and caused a side-effect on us

Eric-B-Wu commented 2 months ago

Hey @sagnik17, I'm looking to investigate this issue; however, don't seem to be able to reproduce it. Can you let me know if you are still running into this issue, and if you are could you send a video of how to reproduce it? attachment

github-actions[bot] commented 2 months ago

We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed.

sagnik17 commented 1 month ago

Yeah, looks like, it working for me now. not sure but earlier, I tried multiple times, and I was able to repro the issue.

github-actions[bot] commented 1 month ago

We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed.

github-actions[bot] commented 1 month ago

This issue has been closed because the information requested wasn't provided within 7 days.