Share via

Missing webhook notification for new emails intermittently with active subscriptions

Aarsh Patel 0 Reputation points
2024-05-14T11:52:34.06+00:00

We have created azure function which will get triggered for new email and process it. But for some strange reason some times it is not getting triggered for some mails. So to resolve that we had to create missing function which will check if there is any unread message which was not processed earlier. Is there any work around to this ?

Thanks in advance.

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,408 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. LeelaRajeshSayana-MSFT 13,871 Reputation points
    2024-05-15T00:23:29.07+00:00

    Hi @Aarsh Patel Greetings! Welcome to Microsoft Q&A forum. Thank you for posting this question here.

    If you have use Azure Logic Apps When a new email arrives event and trigger the Azure function based on that, I would recommend inspecting the run history of the logic app to see if the logic app gets triggered for the emails which did not get processed. The run history would also provide more information on why an event in the workflow might have failed.

    If there are many emails sent at the same time, some emails could be missed by the trigger due to underlying system limitations.

    If you see any throttling errors in Azure Logic Apps logs, consider Scaling the logic apps

    A webhook or HTTP trigger function might require an acknowledgment response within a certain time limit; it's common for webhooks to require an immediate response. The default time out for a Consumption based Azure function is 5 minutes and the maximum setting allowed is 10 minutes. Please refer to the Function App timeout settings for more information.

    If your Azure function is processing emails that have any large attachments or if the processing time is higher, it is highly likely that the function gets timed out before performing its task. Consider using a trigger like Service Bus Queue Trigger which does not need an acknowledgment response from the Azure function, to overcome this issue. Here is a reference to the article for Setting up long running queries with Azure functions which provides details on how to set this up.

    If you are using a different approach to handle the incoming emails, please feel free to share more details and we would be glad to assist you further.

    If the response helped, please do click Accept Answer and Yes for the answer provided. Doing so would help other community members with similar issue identify the solution. I highly appreciate your contribution to the community.