Desktop Flow - Send Email Working on my local, not working when running in server.

[gaurav-cointab]

I have built a flow in Desktop Flow. Where I am sending email via AWS SES SMTP Settings. That flow is working properly from my local machine (Windows Home 11). I am able to send email from it. Properly.

Now when I am syncing the flow from my local to cloud, and then to the server (Windows Server 2019 Datacenter, AWS Hosted), then it is not running there.

Email is not going. I have checked tenet is working to the hostname and port of the SMTP settings. I have checked that there is no IP restriction in the AWS SES SMTP Settings. There is no restriction to the outgoing settings of the server.

Now what can be the reason for this not working, if it is working on my local machine.

[Nived_Nambiar]

@gaurav-cointab 

Any error is shown ?

[gaurav-cointab]

This the screen shot from the monitor section.

And this is when there is no expression in the send email. All the values are hard coded.

What can be the problem...

[gaurav-cointab]

@Nived_Nambiar 

[Nived_Nambiar]

@gaurav-cointab 

Are you sure that error is coming while sending the email ?

[gaurav-cointab]

Yes, this is wierd. That is why I send the screen shots of the error from the panel. I can send the screenshots of the smtp settings, and the email settings. They are working on my local machine, but not working on AWS EC2 Windows Instance (Windows Server 2019 Datacenter). Could the elevation permission be any issue, because I am facing 1 more issue. Which is this.

I am opening the chrome window, and the trying to save a file, and I am controlling the folder in which it is getting saved by controlling the "Save As" window. Now what is happening is this. If I run the flow directly from the server physically, then that window is clicked and I can send keys to it. But when it is running by cloud flow triggered automatically, then it is not able to click on the "Save As" window, and not able to send keys to it. I can attach the screenshots for that also. So I read somewhere that there might be some problem with the elevation permission. So I am also trying to figure it out. If you have a solution for that also, it will be helpful.

But could that be affecting send email? Or it it something else?

@Nived_Nambiar 

[Nived_Nambiar]

I think that may be issue. After researching on AWS  EC2 elevation issue, I got to see that it may effect smtp part as well [ not sure , saying based on information i got]

You can try to resolve the problem related to elevation and try again 🙂

Hope it helps 

[gaurav-cointab]

@Nived_Nambiar 

I am not able to resolve this issue. Of elevating the permission for AWS EC2 Windows Server 2019. And I am not able to find any steps online also. 😞 This is becoming a deal breaker for us, as this is very very important of us. Can you loop in anyone from any team, who can help us. We can do screen share and figure out what is the issue? Or I can send all the settings in the portal, as well as the server, so that this can be resolved.

This is becoming a deal breaker for us.

[Nived_Nambiar]

Tagging @v-dezhili-msft  

Requesting your help in resolving issue for  @gaurav-cointab  

[momlo]

@gaurav-cointab 

You wrote you are using "send keys" perhaps this is an issue, and what window is not displayed correctly/visible during unattended runs (remember it runs 720p by default)

You can automate "save as" using a window based on UI elements/actions to make it more reliable and try again.

Also, to be sure there is no actual network/acl issue - did you try sending emails with pure text (no attachments)?

If that works, you know your smtp/network config is ok.

[gaurav-cointab]

@momlo 

I have fixed the AWS EC2 elevation issue, as it was due to my noob understanding of the unattended, attended flow. Now I am able to run the flows with being able to accept the new "save as" window. All that is happening now. But the problem is that I am not still able to connect to any SFTP and not able to send any email. So I defined another way of sending the file. I called some API of mine, and then sent the file via that. So it is resolved now. I have tested the email in multiple ways, and even tries what you suggested, and then only came on this platform and they try to get it fixed. But in any case, now I am able to complete the flow.