Question

Workflow emails looping back

Workflow

Updated May 7, 2015

asked on May 5, 2015

Any ideas why workflow is sending two emails for decision #1? When I change the field values to the needed selection for this rule, it will send the email and pause the workflow as it should, but after I edit the document again, and change the final field value for it to to kick in Decision #2, I will get an email based on #1, as well as #2. I only want it to send 1 email per decision.

email_WKF.PNG (13.6 KB)

| Download

0 0

Replies

replied on May 5, 2015

It sounds like you have a starting rule that is firing the workflow a second time when the document has been changed by you. I would take a look to see if that is the case and then make it a little more restrictive.

0 0

replied on May 5, 2015

I do not know how to explain what i am doing, just that starting rules are very similar to the decisions, and there is not away to make it work. If I could find away to show you each and every step on here I would.

0 0

replied on May 5, 2015

If you right-click on an activity, you can turn on activity summaries (under Description Options) so activities will show their properties in screenshots. You can turn that same option on for the entire workflow but right-clicking in the white space outside of the activities. That might make it easier to explain.

1 0

replied on May 5, 2015

Its all in the starting rules, I feel like I do not have enough values to work with.

0 0

replied on May 5, 2015

Ok, what are the starting rules? What are you waiting on in the Wait for Entry Change activities?

1 0

replied on May 5, 2015

Here is an export of the WF. I have some pretty serious stuff I do in LF, and this has been the easiest process to think of but hardest to build to date.

Rename this file to . zip

0 0

replied on May 5, 2015

I removed the WFI because the XML usually contains a fair amount of personal info and this is a public site.

I see what you're trying to do. The easiest way to accomplish it is to use a tag or a field to indicate that the doc has already started through an instance of this workflow. Your starting rule would check that the tag is not assigned. Then as the first step in the workflow, you'd assign the tag. Any other field changes wouldn't trigger the start rules since the tag condition would no longer be satisfied.

1 0

replied on May 7, 2015

this is the fix to the issue -

and the starting rule -

I hope this helps others in the future :)

0 0

replied on May 7, 2015

Thanks for sharing, Curtis.

Was the starting rule previously set to "Entry Changed" rather than "Entry Created"? If it had been "Entry Changed" then that correlates to what John had suspected in that since the document path doesn't appear to be changing, and users are just modifying a field value, in addition to moving to the next step, it is then triggering a new instance of the workflow to run on that same document.

Moving forward though, it's best to review the starting rule conditions and make sure that there isn't a way to accidentally trigger it when it's not meant to be triggered.

Regards

0 0

You are not allowed to follow up in this post.

Question

Question

Workflow emails looping back

Replies

Sign in to reply to this post.