@amytucker714
I've seen this kind of issue before with writing JPG files to Blob storage, there's something funky with the new editor that it mungs up parsing binary/base64 conversion unless the code is edited. I'm not sure if you can do this in Power Automate, but in logic apps in the code designer you can find the email attachment field and remove the outermost curly braces from the contentData string:
"attachment": [
{
"contentData": "@{body('Convert_Word_Document_to_PDF')}",
"contentType": "application/pdf",
"fileName": "Report.pdf"
}
becomes:
"attachment": [
{
"contentData": "@body('Convert_Word_Document_to_PDF')",
"contentType": "application/pdf",
"fileName": "Report.pdf"
}
I don't know why that fixes it but the old editor doesn't add the extra curly braces around your function while the new editor does, iirc it's related to how the underlying engine parses data inside curly braces vs without as it implies some kind of typing that totally breaks things. If you can't edit the code directly you might be able to get it to work correctly by using the Expression editor and selecting the PDF output there instead of using the dynamic expression shortcut (lightning bolt).
