Nope, no problem here - you're safe 
If you set your WF to run on modification, it assumes modification by a non-workflow entity. Otherwise, yikes, that'd go on forever! I have some workflows myself that run "on modification", and then update themselves - ie, updating the title or ID if components changed.
Now you've made me wonder, though .. if there is a conditional start for, say, an updated Title... and another WF runs and updates the Title... it would run, right? Pretty sure it would. Hm, might need to test that, just in case...
Cheers,
Rhia
Yes it will. If a different workflow updates the item then that will start a workflow set to start on modification. This is where the coniditional start on modification comes in.
Hi Ryan that makes sense. So I am fine then. However, if I did not want another Workflow to kick off another Workflow then I could use the "conditional start" feature to customize ?
That's right! So if your current WF is updating the title, you'd want to make sure that maybe the conditional start on the other WF is something like "only start if modifier is not equal to WF service account name"
Di I accomplish a conditional start via the "Start Workflow Action" icon ?
If you're using Nintex on-prem, it's under Workflow Settings:
Scroll down, and you'll see this:
If I select "Conditional" on either "Start when items are created" or "Start when items are modified", I can then enter this kind of logic:
So in this situation, only items that are modified - but are also "resumes" that have a graduation year of "less than 2011" will trigger the workflow.
