Per-type worker concurrency caps

GET

/admin/jobs/concurrency

• Local development behind nginx (port 8088 by default)

Every registered job type with its current concurrency cap (0 = uncapped). Caps live in system_config and are loaded by the worker Pool at BOOT, so applies_on_restart is true — an edit takes effect on the next restart. Gated on system.jobs.read.

Authorizations

• cookieAuth
• bearerAuth

Responses

200

Type caps.

object

items

required

Array<object>

object

type

required

string

cap

required

Max concurrent jobs of this type; 0 means uncapped.

integer

applies_on_restart

required

True — the worker Pool loads caps at boot, so an edit takes effect on the next restart, not live. The UI surfaces this.

boolean

401

Authentication required, missing, or invalid

object

error

required

Human-readable error summary

string

Example

the request could not be completed

Example

{
  "error": "authentication required: sign in and retry with a valid session or API token"
}

403

Authenticated but missing required capabilities

object

error

required

Human-readable error summary

string

Example

the request could not be completed