Job Run Status

glue.get_job_run
ActionAmazon Web Servicesconnection required

Calls the AWS glue API (SigV4).

Read the state of a Glue job run.

Connection

Required
Yes — the node will not save without one
Auth type
API key
Providers
AWS Glue
Secret shape
{"access_key_id", "secret_access_key"}
Config it needs
region
Resolved by
config.connection_id, else node.connection_id

Configuration

3 fields, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
region
AWS region (overrides the connection).
stringNo———
job_name
Glue job name.
stringYes———
run_id
Id of the run to act on, from its Glue URL or console — not its name.
stringYes———

Output

One shape.

result

FieldTypeExample
job_run_id
string—
job_name
Name of the job this run belongs to.
string—
previous_run_id
Id of the run this one retried or continued, when there was one.
string—
trigger_name
Name of the trigger that started this run, if any.
string—
log_group_name
CloudWatch log group holding this run's driver and executor logs.
string—
profile_name
Glue usage profile the run was launched under.
string—
state
string—
state_detail
Longer explanation of the current state, if any.
string—
error_message
string—
started_on
When the run started, epoch seconds.
number—
completed_on
When the run finished, epoch seconds; null while it is running.
number—
execution_time
number—
{
  "completed_on": 0,
  "error_message": "",
  "execution_time": 0,
  "job_name": "",
  "job_run_id": "",
  "log_group_name": "",
  "previous_run_id": "",
  "profile_name": "",
  "started_on": 0,
  "state": "",
  "state_detail": "",
  "trigger_name": ""
}

Related AWS Glue nodes

See Job Run Status run in a workflow.

In a technical demo we add the AWS Glue connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.