Quick Flow Bug: email notifications about errors or input required when a flow ran successfully

I’ve built a flow automation that is meant to interrogate inbound emails, in this particular case in Gmail, then analyze the inbound emails and based upon the content, draft responses and send those responses out. Unfortunately, because the platform doesn’t allow for automated sending requiring a human in the loop, I built a step at the end of this flow that would normally require a human input. I then chain a trigger to it to allow it to send the email notification out if required.

However, effectively this intelligent auto responder doesn’t always need to send email notifications based upon emails. It found my inbox. Currently the flow runs on a regularly scheduled basis, it fires correctly, and doesn’t need to take any additional action because it didn’t find an email that need to be responded to. Effectively the flow itself is working as advertised and in the flow history shows that it successfully ran, didn’t require any response. Follow up and close down.

However, I continue to receive after each run a notification in my inbox that there’s human input required as seen below. This is nothing but noise, it isn’t an actual error, there is no way to disable this notification, as well as there’s no way to further debug a flow because there’s no debug logs to be able to identify what’s causing this trigger for the email. No, this email is an auto response from AWS quick. It is not part of my flow, it is not effective, it is not required because there was no human in the loop required in this particular case because the conditions didn’t require such. This is an utter bug in the platform.

Email content scene below

you’ll note that I’ve already enabled as part of my trigger and auto confirmation as seen below:

Worse yet, you’ll see that it doesn’t reliably fail as you would expect. It’s random in nature. It’s outside the control of a human and it’s just an unreliable quick platform.

This might even be multiple defects that I’m hitting in one particular flow, but as a new platform user, I’m struggling with the quality of this platform and any help or better yet escalation to the product team would be valuable.

Hi @Michael_Kleinberg and welcome to the community!

This is definitely an interesting situation you found, and thanks for providing so much detail in your post. I think you are correct, that this is a genuine bug you’ve encountered, so I would recommend opening up a support ticket with the AWS team to get more assistance on this. (here is the link to do so: Case management - AWS Support.)

Hope this helps and feel free to keep us updated on any new developments/questions you have regarding this bug by replying to this thread.