Get Pending Job Executions
iot_jobs_data.get_pending_job_executions
ActionAmazon Web Servicesconnection required
Calls the AWS iot_jobs_data API (SigV4).
Gets the list of all jobs for a thing that are not in a terminal status. Requires permission to access the GetPendingJobExecutions action.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- AWS IoT Jobs Data Plane
- Secret shape
- {"access_key_id", "secret_access_key"}
- Config it needs
- region
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
region AWS region (overrides the connection). | string | No | — | — | — |
thing_name The name of the thing that is executing the job. | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
inProgressJobs | array | — |
queuedJobs | array | — |
{
"inProgressJobs": [],
"queuedJobs": []
}Related AWS IoT Jobs Data Plane nodes
See Get Pending Job Executions run in a workflow.
In a technical demo we add the AWS IoT Jobs Data Plane connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.