capabilities.work

Trigger Job Run and Wait for Output

A 3-step recipe with Databricks. We can help you get access.

Recipe · 3 steps

Trigger Job Run and Wait for Output

with Databricks

Run a job now, wait for completion, and return its output.

  1. Trigger an immediate run of the job, optionally overriding notebook parameters. Returns the globally unique run_id.
  2. Read the run metadata and inspect the life cycle state. Loop back while the run is PENDING or RUNNING; continue once it is TERMINATED.
  3. Retrieve the output and metadata of the completed run, exposing the notebook result and any error trace.
What you'll need to have ready
  • job_id: The canonical identifier of the job to run.
  • notebook_params: Optional map of notebook parameter name/value pairs.
  • idempotency_token: Optional token guaranteeing run idempotency.
For your developer

Arazzo workflow databricks:run-job-and-wait, 3 operations: runJobNow → getJobRun → getJobRunOutput. Specs on APIs.io.

More recipes with Databricks

Audit Cluster Lifecycle EventsCancel a Job's Active RunCancel Job Run and Confirm TerminalInspect and Recursively Delete a DirectoryClone a Job From an Existing OneCreate Job and Trigger First RunDrain Active Runs Then Delete JobEdit Cluster Configuration and VerifyExport a Notebook and Re-Import as a CopyFind Terminated Cluster by Name and Start It