This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
The answer to this question is pretty much that it depends on the structure of your data going into the email tool, so I think we need to know that before we can truly answer your question.
For example, if your recipients are physically listed in the email tool, we'll have to approach solving this problem in a very different way than if they are referenced dynamically from a field.
In the latter scenario you would do some basic transformation to bring the data into the structure you require, as shown below and in the attached example.
The comma seperated list is a way of sending the same email to different recipients so we must then split these up using a text to columns tool, then it's a case of using a formula tool to generate todays date.
Yes that's a fair response, this was something I was thinking about; when the email doesn't send does the Email tool produce a red (i.e. fatal) error, or does it just give a soft warning in the results window?
If it's the former, we should be able to build in some logic to our current workflow, if it's the latter then we may need to make use of the 'CReW macros' in order to execute the email workflow and then run a second workflow which reads the log of the first workflow, and parses out any information regarding emails not sending.
I guess in this case the emails are sent, so I would agree with Alteryx on this front, the messages were sent you just got a bounce back. Unless you create a way of monitoring your inbox (which is possible with Alteryx, check out some macros on the Alteryx Gallery), then I'm not sure what you can do, nor expect Alteryx to do in this case.
Sometimes the tool will fail to send emails within Alteryx, say for example, you have no internet connection, or something like that, you'll be able to catch these cases with the logic shared above, in this scenario I guess either all the emails are sent (unless the internet connection drops mid-way through sending them), or no emails are sent, in which case you can just remove all records from your workflow.
You can break your piece into two workflows...
1. Send emails and generate table of 'emails I think I have sent'
2. workflow that gets information from logs to find out if the tool did send all/no emails, pull records out if so, also monitors inbox to check if you have any bounce backs, if so pulls those specific records out of the input generated in step 1.