We have extended our Early Bird Tickets for Inspire 2023! Discounted pricing goes until February 24th. Save your spot!

Alteryx Designer Discussions

Find answers, ask questions, and share expertise about Alteryx Designer and Intelligence Suite.

Email Tool - Corrupted Attachment

jsdn14
7 - Meteor

Hello all,

 

I'm facing a problem with the email tool, mainly with the attachment option.

I need to attach a word document to send several emails, the problem is when I sent the emails the files are corrupted and people can't open it, I tried converting to pdf but no success and also I tried saving the files in One Drive but didn't work.

 

jsdn14_0-1574354559017.png

 

I'm curious because when I attached an excel file then the people receive the email with the attachment working correctly.

Below is a screenshot of the error, the file in my computer works well and I can open it without any problem so I don't know if it's something Alteryx does when sending the email:

jsdn14_1-1574354795947.png

 

Please let me know if you need more details and thanks for the help!

 

20 REPLIES 20
Bobbyt23
7 - Meteor

Thanks, for some reason I can't see those images. Would you be able to attach a workflow for me to look at?

pdxsvrider
7 - Meteor

I just made this sample workflow that emails me an excel file and the file opens without any issues. Just be sure to change the email settings in the configuration. Also, don't forget to update where you save the file to.

ntobon
Alteryx
Alteryx

Defect

DE21917 - Using Email tool and receive error: 

 

Email (2) Record#1: Failed sending data to the peer

Description:

In 2019.3 the Email tool throws an error when a comma is used to separate multiple email addresses in the Cc: and Bcc: fields; the To: field works as expected with comma-separated email addresses.

 

Solution:

Open. Defect is target for resolution in future release.

Workaround:

Use semicolons as delimiters.

Bobbyt23
7 - Meteor

Thanks for the response. In this instance I only have one email in the to and from fields. This error only happened when I attached a body field as previously suggested to fix the error. Could there be anything else causing that error?

Bobbyt23
7 - Meteor

An update for you all. The error was being caused by the fact I had spaces in my file name and sheet name! Changing them to underscores has resolved the problem. Hurrah.

HARSHINI
5 - Atom

Thanks for this workaround. It worked perfectly.

ntobon
Alteryx
Alteryx

DE22485- Workflow runs and sends out an email message with a corrupted attachment.
Was Fixed in: 2019.4.8.22007

szabolotski
5 - Atom

A combination of things worked for me:

- Use Block Until Done to create output first and email later (anchors 1 and 2 respectively on the Block Until Done tool)

- Pass on a unique record to populate the Email tool body (and so use a field instead of hard-coding it); use Unique or Sample tool

- Email addresses in the To, CC and BCC lines should be semi-colon separated with no spaces

 

When executed like this, only one email attachment is sent and the attachment is not corrupted.

 

szabolotski_0-1591631257299.png

 

LukaszKarpinski
8 - Asteroid

Hi,

 

I'm using Alteryx version 2019.3.5.17947 and I have the same problem with corrupted attachments. I use "block until done" and render to save the file (pdf) to my shared drive and then I send it using e-mail tool (file directory is provided in the attachment window).

 

LukaszKarpinski_1-1605012237806.pngLukaszKarpinski_2-1605012255370.png

 

LukaszKarpinski_3-1605012660814.png

 

Kind Regards,

Łukasz

 

ntobon
Alteryx
Alteryx

@LukaszKarpinski 

 

- For the corrupted attachment, try the workaround documented in this post. 

 

- For error "Failed sending data to the peer": you are running into a known defect. 

Issue

The Email tool throws error "Failed sending data to the peer" when a comma is used to separate multiple email addresses in the Cc: and Bcc: fields; the To: field works as expected with comma-separated email addresses.

Cause: Defect: DE21917. Status: Open. Defect is target for resolution in future release.
Workaround: Use semicolons as delimiters.

 

 

Labels