What Azure service allows us to run at a fixed interval (IE every 5 min), and if a given Outlook/mailbox folder has one or more emails in it, then send one notification email?
We have a Logic App that does email processing. If the processing fails for whatever reason, the email is placed into a "Failed" folder, and an email notification is sent out. The issue is when a dependent service is down, we are getting hundreds of email an hour.
We tried creating a second Logic App that runs every 5 min, sending email if it found email in the folder that is "flagged", but we still received one email per flagged email.
We are thinking a separate service that runs every so often, and if a folder has email in it, then send out a single email.
Actually there is a Outlook trigger action to detect if there is an email is flagged. It supports to change the Folder,Importance,Interval and add other parameters to match.
And this is the action Optional Parameters description.
Related
I am using a Azure logic app connected with Outlook mail box. I need to trigger it when the e-mail comes to the mailbox other than a single specific from address.
For your requirement, just configure your trigger like below:
And do not add the parameter From
==============================Update===========================
For your requiements, there are two solutions.
1. Create a folder named "From hury shen"(out of "Inbox" folder) and create a rule in your outlook to filter all of the emails from Hury Shen to this new folder.
After that, I test it in my side, the logic app will not be triggered when a new email from hury shen arrives.
2. The other way is to add a "Condition" in your logic app. If From address equal to the specific email address, do nothing. If From address not equal to the specific email address, do what you want.
I have a weird hard-to-replicate issue with Graph API and Outlook subscription endpoints. A user is authorised in my app and subscription is created for me/messages with change type created.
Everything works fine in 99% of the cases, but once in a while the endpoint is triggered several times with the same email. There is no changes to the email or any other part of the request, except ID, even timestamp. I have no idea how to replicate it consistently and/or fix an issue. Is there any scenario where Graph API would send the same message twice with slightly different IDs? It looks like they are sequentially generated IDs too, as they differ by 1-3 characters in the very end.
As described at https://support.google.com/datastudio/answer/9263641, there is now the Scheduled Email feature for Google Data Studio Reports.
We tried to set up a scheduled email in my organization and we noticed that the emails do not work for anyone except the person who set up the schedule. All emails have been verified to be correct and all users receiving the email have access to the underlying data source(s) (not sure if that matters though).
What do we need to do to get the scheduled email working for additional recipients? Even if it was only 1 other email, we could set up an email group and handle getting it to everyone that needs it.
This isn't actually an issue, after further investigation these emails were being caught by my company's spam filter. Once I whitelisted data-studio-noreply#google.com, I was able to receive the messages.
When using Azure Logic App Office 365 Outlook connector - "Send an email", is there a way to find out if the email was actually delivered or not to the recipient so as to take a specific action based on the failure?
I used an invalid email ID in the connector, but the action of sending email is shown as successful even though the email was not delivered. To confirm it is an invalid email ID, I sent email to this invalid email ID from my Outlook and I received an undelivered email message.
In the next action after this “Send an email” action, I selected the 3 options (has failed, is skipped, has timed out) under “Configure run after”. However, this action is never executed as the email sending action is always successful even though the email was never delivered to the user.
Below is a screenshot of my logic app. The bottom right action in yellow is never executed even though the email is not sent in the previous step.
Send Email Logic App
Any inputs on how I can find out if the email was actually delivered or not?
My goal here is to find out if the user actually received the email or not, and then take some action if the email delivery failed.
No, this is not possible from within the Logic App.
The only way to occasionally accomplish this is to monitor the sender inbox for NDRs (Non-Delivery Receipt). This can take minutes to hours.
Be aware, a number of email systems will not even send NDRs as they can be used to fish for email addresses.
You can use get emails action to get the latest email and you can perform the next action based on the condition whether the subject of the email we get contains the "Undelivered" string.
Sometimes it takes long to receive the undelivered report email in outlook. so i made a specific flow which will extract the wrong email that i sent the mail to and send me an adaptive card with that email provided in it.
I am using cakephp framework for my web application development. My application will send welcome email after user entering his information. After this only it will display 'Sign Success' message. Unfortunately CakeEmail taking around 6 seconds to send a mail, so my sign up approximately taking 8 seconds. So how can I speed up the sign up process without removing CakeEmail.
You should defer sending of the email so that the user doesn't have to wait for the email to be sent before rendering any content. Whether the email has been sent or not makes no difference to the user seeing your 'Sign Success' page so shouldn't be responsible for increasing page response time.
Take a look at using something like the Queue plugin for CakePHP to defer sending of email. This would allow you to log that an email needs to be sent after the user's data has been saved. You'd then setup a task for sending the email. The task would executed the next time the queue is run (for example, by a cronjob).