Drawback: A SP 2013 WF set to start out when an merchandise is modified on a Contacts record doesn’t begin robotically if a subject for that record merchandise is up to date by one other workflow; nevertheless, it does begin robotically if a consumer edits the record merchandise.

Set-up: I’ve three lists (Duties, Contacts, and Funds) and two fundamental workflows that work on this order.

1. Process record: When an merchandise process standing is modified manually by a listing consumer, a SP 2013 WF determines whether or not the duty is newly accomplished. If that’s the case, it’ll add 1 to the entire variety of accomplished duties and replace the entire on the Contacts record for consumer to whom the duty was assigned. This WF is working FINE.
2. Contacts record: When an merchandise is modified, a SP 2013 WF is meant so as to add a process to the Funds record when the consumer’s accomplished process whole reaches 1, 3, and 6. This WF works fantastic if the consumer edits an merchandise , however doesn’t begin when the merchandise is up to date by the WF working on the Process record.

What I’ve discovered and tried:
I’ve learn threads that appear to point that the workflow on the Contacts record will not run as a result of the merchandise is being up to date by the System Account, however I do not know methods to affirm that or methods to work round it. I have not tried rebuilding this as a 2010 workflow, however I’ve tried enabling the Website Function “Workflows can use app permissions” and placing the replace merchandise on the Contacts record motion inside an “App Step” as urged right here, but it surely would not make a distinction.

I believe this tread appears to deal with the identical concern, however is unresolved. And I do not even know what this one is speaking about, but it surely additionally appears associated: SharePoint occasion receiver ItemUpdating occasion behaves in a different way when a listing merchandise is up to date by means of Workflow