we see in the orchestrator log that email has been sent, but we dont receive any email.
when we tried manually we are able to send email. we are using Outlook and send email activity.
Appreciate if someone can share their experience on this.
Did we try with SEND EXCHANGE MAIL ACTIVITY where we can mention the credentials of outlook
The properties to be mentioned are
The server Usually is âhttps://outlook.office365.com/EWS/Exchange.asmxâ,
username should be âuser@company.comâ, and mention the password.
in ExchangeVersion, usually latest is good for Office365
But before to that check with outbox in your outlook
Is it showing status as connected online
How the orchestrator says that the email has been sent, you must be using log message for that, thatâs not sufficient to assume activity worked well.
Ideally if it is not working, it should throw error. Please check if âContinue on errorâ is on for that activity? Check that k properties panel and if checked, par uncheck that selection.
Try on debug mode and check if thereâs any error. If you are able to send manually then the password it not an issue. Otherwise, the activity will do its job and proceed but as outlook is waiting for new password to be updated, itâll make the emails stay on outbox until password is updated for outlook. Par hage a check on the password too.
Also, can you confirm if you have the, enable script action as on?
Below link would help you to get started for settings part.
Outlook send email got started working automatically, The activity got passed while Robot was running and sending email and we did not see any error or any emails in outbox. Unfortunately we could not find the reason behind it. we could not replace outlook with SMTP or exchange as the code was in PROD.
if you say it is in prod then you should dissect this issue, that might reappear as it disappeared, automatically.
Check your event viewer logs and see if you get anything there.
The machine has outlook and itâs a VM, so chances are that the outlook wasnât working due network related issue. Youâd get the details in event viewer.