I have an automation that when a work item is created, an email address is entered into a custom field and then an email should be sent using that email address in the custom field. But I am having an issue sending that email. the custom field is {{issue.customfield_10212}} which I have tried and I even tried hard coding the email address in the TO field as a test. But I still get this error message: Unable to send emails to any recipients. This may be for data privacy reasons, or because of the way these recipients have configured their email accounts. I added a log action to see if the email address is showing and it does seem to be. Not too sure if there is a solution to this or perhaps a different field type?
There is a long-standing, racetrack timing defect with the Work Item Created trigger (among others) where the rule can start running before the item is in a stable state. That is, missing data leads to unpredictable condition / action results, strange errors, etc. For your rule, this could cause the custom field to be empty when the rule attempts to use it.
Atlassian knows about this problem, and was reportedly working on architectural fixes for it for many years, with no forecasted resolution timeframe.
The mitigation for this symptom is:
Please try adding a re-fetch after the trigger and test your rule again.
Kind regards,
Bill
I am not really surprised this is still unresolved, because this touching event consistency architecture and it's not some small Bug. Rather Backlash and effects actual Architecture Solutions.
Cloud already has enough latency as it is, and fixing this properly would likely require Atlassian to change how Automation behaves at a pretty fundamental level.
Hopefully Atlassian gives these real platform issues more attention as well, not just AI-related work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy thank you for this, I have added the Re-Fetch action after my trigger but unfortunately I am still getting the error for the email that should be sent off.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information, @Drishti Maharaj Let's gather more evidence to help understand this symptom...
#1) What is the type of your customfield_10212: text, select-option, etc.?
#2) Please post images of:
Please note there was a similar question / symptom about two months ago and that was caused by a production incident in Atlassian tools. Thus, you may want to submit a ticket to Atlassian Support while this community tries to help.
You are a Product Admin for a paid license level and may submit the ticket here:
https://support.atlassian.com/contact#/
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Bill Sheboy thank you - I have submitted an Atlassian support ticket as I tried a few other options yesterday with no luck.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When you submit / update the support ticket, you may want to include a link to this community thread as that will show what has been tried. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Drishti Maharaj
Thanks for the screenshot.
Did you tried new ”Send Customized Email” Action ?
Atlassian’s current docs say Send email is deprecated and Send customized email is the supported action. That newer action supports smart values, custom fields, and external recipients, but Atlassian also notes that some emails can still be blocked by policies such as filter content or external user security.
Quite interesting topic. I wonder on what Points others.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi. I am using the customized email action yet it is still continuing to error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.