Thresholds Explained: Triggering Jobs Based on Conditions
Thresholds in OpCon look similar to Resources on the surface, but they serve a fundamentally different purpose. While resources control how many jobs run concurrently, thresholds are condition flags. They let you build OpCon automations that respond to dynamic states: "Run this job when that number reaches a certain value." Once you understand thresholds, you'll find uses for them in several places.What Is a Threshold?A threshold is a named object with a numeric value. Unlike resources, thresholds are not automatically managed by OpCon. Their value stays exactly where you set it until something explicitly updates it. That update typically comes from an OpCon event, an API call, or an external system interaction.Thresholds are found in the same place as resources: Administration > Library. Create one with a name and starting value (often 0).Threshold Dependencies: Flexible Condition LogicWhen you add a threshold dependency to a job, you're telling OpCon: "Only run this job when the t