Email with attachment
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2024 10:58 AM
I'm attempting to automate a catalog item such that a user requests it, an automation runs and then attaches a .csv file to the RITM, and then my flow will use that attachment in an outbound email. Everything seems to work until it tries to send the email out. You'll see by the attached screenshot that I get a 'Missing start boundary'. I don't know what that means and have yet to find anything about it. Any thoughts?
this is in Xanadu.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-14-2024 12:23 PM
Hi @stevenm - The "Missing start boundary" error typically occurs when sending an email with an attachment due to issues with the MIME formatting in the email's content. Have you tried sending the email with a different attachment, or with no attachment?
It might be helpful to share your script here.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2024 05:43 AM
We have tried two different file formats and neither worked. They both get the missing boundary. I don't have the script. We trigger our automation team to create what they need to create. They then attach a file to the RITM at which point my process can pick that up and send it out. Except that it creates the email, which I see in the emails log, but it doesn't actually send the email out due to this error. I'm still working with my other analyst to see if he can send a different format.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2024 06:56 AM
Did you test sending the email with no attachment?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-20-2024 10:56 AM
Yes, tested with no attachment and tested saving off the attachment. Running a new request and adding that saved attachment back. Both worked. So there's something in the way that attachment is being generated on our automation side of things.