GetAdapterPoolQueue
Shows what an adapter pool has queued and what it currently has leased out.
Examples
Basic usage:
octo-cli -c GetAdapterPoolQueue -id "670000000000000000000001"
Output as compact JSON:
octo-cli -c GetAdapterPoolQueue -id "670000000000000000000001" -j
Options
| Short | Long | Required | Description |
|---|---|---|---|
-id | --adapterPoolRtId | yes | The adapter pool's runtime object ID |
-j | --json | no | Output as raw JSON |
Notes
The tenant of the active context is the LENDING tenant — the pool is its entity. Every entry names the borrowing tenant whose work it is.
There is no global queue position, deliberately: the pool serves borrowing tenants round-robin, so the truthful answer is the position inside the item's own tenant plus the number of tenants that take a turn first.
Entries that already hold a lease are listed too — they are what the waiting ones wait behind, and they are the only entries carrying a member id. Cancel them with the running-pipeline path, not with CancelQueuedExecution.
Manual (non-pooled) adapters have no queue at all; they execute immediately.
An empty queue is an idle pool, not an error.