Resources vs. Thresholds vs. Job Dependencies — Choosing the Right Tool
OpCon gives you three primary tools for controlling when and in what order jobs run: job dependencies, resources, and thresholds. All three are valid, and experienced OpCon administrators often use all three in the same environment. Understanding the strengths, and the right use case, for each will help you design cleaner, more resilient automations.Job Dependencies: Best for Sequential, Linear ProcessesJob dependencies are the right choice when Job B genuinely cannot start until Job A has finished, and when the order matters. If you're building a workflow where data flows from one process to the next, job dependencies create that hard link. They're explicit, easy to read in the workflow view, and appropriate for processes with a defined sequence.Limitation: Job dependencies wait for a job's final completion state. If a job is configured to restart and repeat throughout the day, a downstream job dependency won't trigger until all restarts are complete, which may be far later than you n