data.runner.list-scheduling-diagnostics ​
List provider-blind scheduling diagnostics for pending coding executions in one runner group.
Explain why pending coding work can or cannot run in one group.
Overview ​
| Property | Value |
|---|---|
| Workflow type | Atomic |
| Library | App-runners |
| Version | 1.0 |
Input Schema ​
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
organization_uuid | uuid | Yes | — | Authenticated organization; injected by the workflow API. |
runner_group_uuid | uuid | Yes | — | — |
limit | integer | No | 20 | — |
offset | integer | No | 0 | — |
Output Schema ​
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
organization_uuid | uuid | No | — | — |
runner_group_uuid | uuid | No | — | — |
group_active | boolean | No | — | — |
items | list | No | [] | — |
total | integer | No | 0 | — |
count | integer | No | 0 | — |
limit | integer | No | 0 | — |
offset | integer | No | 0 | — |
snapshot_at | string | No | — | — |
error | string | No | — | Error-as-field envelope populated when query() raises. |
error_type | string | No | — | Error-as-field envelope populated when query() raises. |
States ​
| State | Initial | Terminal | Success | Auto-advance | Description |
|---|---|---|---|---|---|
done | Yes | Yes | Yes | — | — |
API Usage ​
bash
POST /api/workflows/start
Content-Type: application/json
{
"workflow_type": "data.runner.list-scheduling-diagnostics",
"initial_data": {
"organization_uuid": "value",
"runner_group_uuid": "value"
}
}