My job dependency graph looks like this:

A starts B. B starts C and D and 'joins' with E.

Expected behavior: [assuming everything runs successfully] A should never start before E has completed.
Reality: sometimes it does. And as it performs clean-up of some common folders, this messes up E completely.

Potentially relevant info:

• E can be run as a 'join' job from other job flows, not just A-B-C-D.
• All triggering is performed via "Trigger parameterized builds" (I'm including the parameterized-trigger component to the report as well).