if you go to workflow subscriber tracer in workflow administration , you could see starting rules for each workflow. this way you would be able to see what started the workflow second time.

Hey Amy:

Thanks for the suggestion - I've deleted the scheduled rule on one of my workflows, and I'll see what happens when it's scheduled to run next week.  (Oddly enough, when I have the workflow scheduled to run once an hour throughout the day, it only runs once in these instances.)

Thanks much!

Hmm...also a good idea!  I'll give that a try today as well and let you know how I make out. 

Thanks for all your suggestions!

I expect an update. 

THAT did it!  I was able to get each workflow running once, once I renamed the workflow, published the renamed workflow, deleted the original, renamed the workflow back, re-published the re-renamed workflow and re-created the scheduled starting rule, all of the workflows are now running once at the scheduled time.

Thanks a ton for your suggestions!

I filtered out the events specific to the repository tied to this workflow, and the only evidence of other workflows running is the folder that was modified after the initial workflows ran (and there's actually evidence of the folder changing each time the workflow ran, about 11 seconds apart).  

I have the workflow set to run weekly on weekdays, and I have the scheduled start to be a particular day at 8am, and I also have a Business Process tied to this.  Could there be something in these settings that might be triggering the workflow to run twice in rapid succession?

try to simply, delete your condition, recreate it and publish it.  about a year ago we had a similar issue and this corrected it for us.

I thought removing the starting schedule condition and adding it back might have fixed the problem, but it appears the workflow *still* runs twice at the first specified time, but for every other time in the day where the workflow runs (I have it running every hour throughout the work day), the workflow only runs once (which is why I thought the workflow had previously run successfully).

This one is getting a little weird!

Hey, that's great!  Glad I could help.  :-)

Happy Fiche-ing.

Hi everyone

I'm experiencing the same issue when running a WF (two actually) on a schedule that does some automated tasks for the company.

It's applying duplicate values to my multi-value fields and starting to become a massive problem.

I tried Amy's fix this morning and I hope it will work. 

I'm going to leave this to run on Monday the 17th of September and see what happens.

Any way to troubleshoot this perhaps?