Run job

Description

Triggers a Coalesce refresh job to run using this endpoint

Use Cases

We recommend creating a Run job Task for every "job" within Coalesce.

This way, you can use Orchestra to trigger your data transformation on a cron or event based schedule. This has a number of advantages vs. using an in-built scheduler:

• You can co-ordinate tasks outside of Coalesce, like ingestion tools (for operations that move data to your data warehouse) or reverse ELT tools (for moving data outside of the warehouse)

• You can use Orchestra to trigger jobs across Coalesce Accounts and Projects. This means you can enable a data mesh architecture with a high degree of flexibility around Orchestrating different jobs

• When Coalesce jobs run, Data Warehouse cost is incurred. Running these operations on a schedule you set explicitly ensures these costs do not go out of hand

• You can view both deploy and refresh run jobs from Coalesce in the Orchestra UI for an unparalleled debugging ability

• We aggregate metadata from the Coalesce Task in the same place as the metadata from other operations in your Pipeline

Setup guide

Fetch the environment ID

Head to the "Deploy" page in Coalesce and select the environment in which to run the job in. The ID is shown next to the name of the environment.

Parameters

These parameters are required to run the Job run Task

Name	Data type	Restrictions	Example
Environment ID	Number	N.A.	1

Error handling

API Requests

If we receive the following error codes from Coalesce, we'll raise an error and the task will move to a failed state.

Code	Description	Handling
401	Unauthorised	We will raise an error and parse the raw error message from the Coalesce response as the Orchestra message
404	Not Found	We will raise an error with the HTTP Reason as the Orchestra message
Other error code		We will raise an error with the HTTP Reason as the Orchestra message