Skip to main content

Thresholds and resources

In briefA threshold is a named whole-number value that jobs can wait on; a resource is a named pool of units that jobs take while they run and give back when they finish. Jobs use both through their dependencies, so a threshold gates work on a count or a signal, and a resource caps how many jobs run against a shared system at once.

WhereDesign › Toolkit, on the Thresholds and Resources tabs. Each is created, edited and viewed in a dialog over its list. A resource's row menu also offers Current Allocations, which shows what holds its units in one environment right now and what is still available across every environment, and lets you release units an inactive or deleted environment still holds.

When

  • Use a threshold to hold jobs until a value — set elsewhere — meets a condition.
  • Use a resource to cap concurrency; use Use all on the dependency for a job that needs the whole resource to itself.
  • To make one job wait on another job's outcome, use a job dependency instead.

How

  1. Open Toolkit, pick the Thresholds or Resources tab, and select New Threshold or New Resource.
  2. Give it a Name and a Value (a threshold) or a Total (a resource).
  3. Add a threshold or resource dependency to each job that should be gated by it. The full steps are in Use thresholds and resources.
Notes
  • A job waiting on a threshold shows Waiting: Threshold Dependency; one waiting on a resource shows Waiting: Resource Dependency, and returns there if another job takes the last units first.
  • A Force Start takes no units, so the job does not count against the resource while it runs.
  • A resource's total is shared by every environment. Jobs in one environment can wait while another environment holds the units.
  • Both are workspace-scoped; you see only those in workspaces your role can see. A workflow save checks that you can view each threshold or resource whose dependency it adds or changes.
Watch out
  • You cannot delete a threshold or resource that jobs still depend on; Cross Reference lists them so you can remove the dependencies first. A workflow last saved before this release may not be listed until it is saved again.
  • Deleting a threshold or resource and creating another under its name does not move dependencies to the new one; their next save is refused until you restore it or re-pick.
  • Lowering a resource's total while units are allocated can leave Available (all environments) negative until those jobs finish.
  • Changing a threshold value or freeing units does not re-check waiting jobs at once; they move on a later pass.