Answer
Dependencies should follow the actual business workflow, not just the technical order in which jobs were historically scheduled. That means modeling prerequisites, file arrivals, API responses, restart behavior, approval steps, and exception paths in the same design instead of treating them as separate operational knowledge.
Buyers should ask to see how a platform handles both normal sequence and failure branches. If dependency logic becomes too opaque to review or audit, the tool may create a new operational blind spot instead of removing one.