You are viewing limited content. For full access, please sign in.

Question

Question

Workflows starting twice and causing entry locks

Workflow Version 10
Updated December 20, 2018
asked on December 19, 2018

Suddenly this year, I am seeing workflows that activate twice when starting rules are met.  This time, it appears this is causing Entry Locks on the target documents so that the last activity cannot change the field values.

Previous LF Answers posts suggest renaming the workflow, recreating the starting rules, and that does sometimes stop the second workflows to start, but this time it didn't work.  Is there anything else I can try?

0 0

Answer

SELECTED ANSWER
replied on December 20, 2018 • Show version history

I would add a condition to the Starting Rule of

User Does Not Equal workflow

This would prevent the Workflow user from triggering itself.

2 0

Replies

replied on December 19, 2018

Just out of curiousity, are the document/records showing as duplicated in your repository due to this?

0 0
replied on December 19, 2018

No.  The workflow is only asked to add a date in a field on the two target documents identified by the Find Entries activity.

0 0
replied on December 20, 2018

Have you looked at the subscriber event viewer and/or trace log?  These would be the best place to track down why it is triggering multiple times.

0 0
View 3 previous replies
replied on December 20, 2018 • Show version history

Thanks, Bert:  Not sure if there is a clue in the subscriber, but maybe you can spot something.  Here is a case where the starting rules were checked three times on this test run and the only thing I can see different is it says the User Name was Admin (me, running the test) and twice the user name is Workflow:

>

>

>

 The WF has this connection, so ... ?

The workflow is just one Conditional Decision with just a few activities involved in the two branches:  either set the retention choice as Option 1 if the field was changed to Active; set the retention choice as Option 2 and add a date if the field was changed to Inactive, plus add a closed date to all the documents found in the starting entry folder.

0 0
SELECTED ANSWER
replied on December 20, 2018 • Show version history

I would add a condition to the Starting Rule of

User Does Not Equal workflow

This would prevent the Workflow user from triggering itself.

2 0
replied on December 20, 2018

Huh!  Part 1 solved, thanks Bert!  I ususally do have User Does Not Equal Workflow on my WF's, but that one did not have it.

Part 2 - it still did not add the closed date to the two test documents in the target folder, even though the Find Entries activity did find them.  Any ideas?

0 0
replied on December 20, 2018

The workflow acknowledges the right starting entry, the target folder.

It acknowledges that it found the two entries inside the target folder.

It acknowledges that those two documents meet the requirements for the righthand branch:

But the two documents do not end up with the new field added with today's date.

0 0
replied on December 20, 2018

AH, never mind!  I solved it myself!  Wrong setting on the add field value activity.  It was set to add the date to the starting entry.  (!duh!)  Ugg.  

Thanks, Bert!

1 0
replied on December 20, 2018

Glad that you were able to track it down.  I have over looked changing the activity entry a time or two myself...

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...