Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Finance | Project Operations, Human Resources, ... / Workflow emails failin...
Finance | Project Operations, Human Resources, ...
Answered

Workflow emails failing on Purchase Orders created prior to MFA being enabled

(0) ShareShare
ReportReport
Posted on by PaulaY 50

We enabled MFA in GP and since then any Purchase Orders that are recalled because they need a change order made to them and resubmitted to the workflow, the approval emails are not being sent. When the workflow manager delegates the PO in GP they are prompted to select their MS account, they select it and then get "An unknown error has occurred". They Hit Ok, the PO goes through the workflow but the approval emails are not sent.

However, any new POs that are created since MFA, email approvals are being sent and received.

Our workflow setup uses Anonymous Authentication and our SMTP server is an outlook.com address.

When I use the Test E-Mail button in the Workflow Setup window, I don't receive an email.

Categories:
Microsoft Dynamics GP
  • Verified answer
    Derek Albaugh Profile Picture
    Derek Albaugh on at
    RE: Workflow emails failing on Purchase Orders created prior to MFA being enabled

    That's exactly the 'bug' I was referencing. When Modern Auth is enabled, recalling a workflow that has been previously completed/final approved, will cause GP to hang/loop.

    Web Client isn't a valid test as email does not work at all when Modern Auth is enabled, in Web Client. This was changed in the Oct 2022 / 18.5 release:

    GP185EmailWC.JPG

    Any emails for Workflow coming out of Web Client prior to 18.5, are most likely using the SMTP server and account setup in Workflow Setup window. This would also be true if you're taking action on workflows through email links/Web Services. 

    This bug itself, didn't make the Oct 2022 release and is scheduled to be fixed in the year-end release, coming around December or January 2022.

    Thanks

  • PaulaY Profile Picture
    PaulaY 50 on at
    RE: Workflow emails failing on Purchase Orders created prior to MFA being enabled

    Thanks for the information Derek. We are currently running 18.3.1200 and are planning an update in the next couple of months. This issue only started to happen for us when we enabled MFA. We have no issues recalling POs in the web client. Our .NET framework is 4.8

    Anything else we can check?

    We plan to wait for the year-end release that will hopefully have the workflow issue resolved.

  • Suggested answer
    Derek Albaugh Profile Picture
    Derek Albaugh on at
    RE: Workflow emails failing on Purchase Orders created prior to MFA being enabled

    There's a couple of things you may be running into.

    First, there is a documented issue with GP when you recall a workflow that has been 'Final Approved'/'Completed', the workflow itself will recall but the recall emails don't get sent out to the originator and/or approver, while if you recall a workflow that has not been 'Final Approved'/'Completed' those recall emails work fine. The fix for this issue didn't make the Oct 2022 release and we're hoping to get it into the year-end release.

    For the 'Unknown Error' when emailing, I'd be curious if users can email anything else from within Dynamics GP, not including workflow emails?

    The reason I ask is, when you enable Modern Authentication, all workflow emails will then be using the account specified by the originator or approver when prompted, it does not use the SMTP account or server in the Workflow Setup window, besides the test emails.  The exception to this is if you're taking action on the workflows via the email links/Web Services, as Web Services doesn't use Modern Authentication at this point, thus will default to what's in the Workflow Setup window.

    There's a number of causes for the Unknown Error when emailing through Modern Authentication, the most common we've seen recently, is the server or workstation is not on .NET Framework 4.7.2 or higher, which is required.

    Thanks

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing Our 2025 Season 1 Super Users!

A new season of Super Users has arrived, and we are so grateful for the daily…

Vahid Ghafarpour – Community Spotlight

We are excited to recognize Vahid Ghafarpour as our February 2025 Community…

Tip: Become a User Group leader!

Join the ranks of valued community UG leaders

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 292,516 Super User 2025 Season 1

#2
Martin Dráb Profile Picture

Martin Dráb 231,401 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

End-of-life Announcement for Microsoft Dynamics GP

Product updates

Dynamics 365 release plans