Workflow starts completely unrelated object

Discussion created by Michael_Lowry on Oct 4, 2017
Latest reply on Feb 13, 2018 by Michael_Lowry
In a recent comment, I mentioned something that happened a few times: a workflow executed objects that it should not have executed. The objects executed are are not in the workflow. They are not mentioned in the workflow. (I exported to XML to double-check this.) They are not even in the same folder. Unfortunately, I had tracing turned off, and Automic Support was unable to explain the reason for the problem. I am unable to reproduce the problem. (And considering the seriousness of the problem, this is mostly a good thing; but it does make troubleshooting difficult.)

Has anyone ever seen an instance of an object like a JOBP executing a completely unrelated object?