Hi! Do you know if there are any limitation towards aliases in automation actions ? I tried to perform the same action on my personnal adress and a gmail alias, the alias test never arrived on my inbox 😞

Sorry a bit unclear what you tried. You created two different automations? OR one automation to hit two emails?

@Kevin Kho i created 2 automations with the same triggers, when i enable the one on my personnal address it works fine, but the one with an alias redirecting to my team and me never arrived in our inboxes I'm trying to figure out if this is due to prefect failing to send the notification or gmail failing to redirect them

Can you answer those questions to provide more info for further investigation? 1. Does it mean that you have 2 automation actions reacting to the same state transition event? 2. What happens if you only use the one that you need (the team’s inbox). Does it fail to deliver the message to your inbox? 3. Is it happening only with email automation actions or with all actions? You could test it e.g. by using a different action such as Slack/Teams etc.

Sorry for the confusion: 1. i created 2 automation but tested them one at a time 2. the alias to the team's inbox never delivered the message, but still I'm not sure if it's prefect that failed to send the email or the alias that failed to redirect because it's from prefect (although, the alias worked fine when sending a email myself), I tested these both by triggering flow and from the debug option 3. I switched to slack notifications and it worked great, I'll probably stick to this for now

awesome, LMK if you have any further questions about this or anything else

thanks, I'll investigate a bit more if the problem comes from the alias doing some kind of filtering 🙂