Run an Existing Job and Wait
A 3-step recipe with Azure Databricks. We can help you get access.
Recipe · 3 steps
Run an Existing Job and Wait
with Azure Databricks
Trigger an existing job with parameters and wait for the run to finish.
- Confirm the job exists and capture its name before triggering a run.
- Trigger an immediate run of the job, passing any notebook parameters and idempotency token, and capture the run_id.
- Retrieve the run state. Repeat until the run life_cycle_state is TERMINATED, then branch on the result_state.
What you'll need to have ready
- token: Databricks personal access token for the Authorization header.
- jobId: The canonical identifier of the job to run.
- idempotencyToken: Optional token guaranteeing idempotency of the run request.
- notebookParams: Map of name-value pairs passed to notebook tasks.
For your developer
Arazzo workflow microsoft-azure-databricks:run-existing-job-and-wait, 3 operations: getJob → runJobNow → getJobRun. Specs on APIs.io.