Dynamics Community Forum Thread Details

Workflow Job Owner listed as my user record instead of SYSTEM when using Launch Workflow via Journey

Hello all -

Back in March I created a workflow that would deactivate any contacts that joined a Hard Bounce segment and send an email to the contact owner letting them know. The workflow is set up as an On Demand, Org level scope with no triggers. It is launched via journey tile once someone joins the segment. At the time I tested and was able to receive the emails for my fake contacts - in other words, it worked. That was right when COVID was hitting hard, so rather than add another communication to our people at the time, my boss asked me to hold off on implementing.

We planned to communicate the update last week and make all live, but since it had been a while, I wanted to test again. The workflow is now NOT working because it is using my name as the job owner rather than the SYSTEM user, and my user record does not have permission to send emails. I have the owner of both the workflow and journey set to LBMC Solutions (our intenal all-access user used on other triggered workflows to send emails), and the workflow is only launched via the marketing journey.

A few other notes that may or may not play into this:

1. The SYSTEM user is disabled for some reason. However, it continues to create contacts just fine when forms are submitted.

2. We received a communication from Microsoft that starting May 11th, D365 Marketing would begin using the SYSTEM user instead of MarketingServices ApplicationUser to make changes to marketing-related records. Our environment was already using the SYSTEM user, so I did not think this would affect anything.

3. Below is a screen shot of an older workflow appropriately using the SYSTEM user as the job Owner. My current workflow is set up the same way but using my name instead.