Forum Discussion

KevinSJC's avatar
KevinSJC
Copper Contributor
Jun 18, 2019

Workflow notifications by email just started to fail

Hi!

 

I built this site a year ago on SharePoint Online, and it has been working great up to about a week or so ago. The workflow has 2 email notifications that fire upon submission of a new form. The first email notification does go out, I am BCC'd so I see them. The second email doesn't always go out. There are no errors recorded by the workflow, it just completes. Obviously something changed, but not on my end. 

 

  • I tested the form with a test submission and both emails were received.
  • I then had an end user submission shortly after, both emails came through.
  • Then later, 3 other submissions came in, but ONLY the first email was received, the second did not.

I know the workflow is technically correct as it worked great for a whole year, and did so with my testing. I changed nothing over the last year. I have no clue what to look at where SharePoint is hosted on O365. 

 

Thoughts? I was hoping for some logging somewhere for email notifications, but I'm not finding anything.

 

Thanks, Kevin

6 Replies

  • NiteshRanjan's avatar
    NiteshRanjan
    Copper Contributor
    Could you let know are these workflows 2010/2013? How many instances of the workflows are in progress? We haven’t hear any issue on our tenant so far. Could we think for use flow as alternative or even recreating the workflow.
    • KevinSJC's avatar
      KevinSJC
      Copper Contributor

      NiteshRanjan, it is a 2013 workflow with only one instance. It fires for new submissions and any modifications, made to complete every time. I am assuming the email is firing, but not getting to me for some reason, thus my reaching out looking for ideas on how to troubleshoot. 

       

      Weird thing is, one that failed last night just worked this morning after I manually started the workflow.

       

      Thanks, Kevin

      • Matt Coats's avatar
        Matt Coats
        Iron Contributor

        KevinSJC I would consider NiteshRanjan's suggestion to consider using Microsoft Flow. Flow does a pretty good job of letting you know why a step might have failed, and Flow is generally a better tool than SP Designer's workflow toolset.

Resources