Run job
Description
Triggers a run of an orchestration job in Matillion.
Use Cases
We recommend creating a job for every "published Pipeline" within Matillion.
This way, you can use Orchestra to trigger your ELT on a manual or event based schedule. This has a number of advantages vs. using Matillion's in-built scheduler:
You can co-ordinate tasks outside of Matillion, like other Matillion ETL jobs or tasks in other pieces of infrastructure like AWS EC2 using Orchestra
When Matillion Pipelines run, Data Warehouse cost is incurred. Running these operations on a schedule you set explicitly ensures these costs do not go out of hand
We aggregate metadata from the Matillion DPC Task in the same place as the metadata from other operations in your Pipeline
Setup guide
Parameters
These parameters are required for this Matillion ETL task:
Name | Data type | Notes |
---|---|---|
Group | String | |
Project | String | |
Version | String | Default = 'default' |
Job name | String | |
Environment | String |
Error handling
API Requests
If we receive the following error codes from Matillion ETL, we'll raise an error and the task will move to a failed state.
Code | Description | Handling |
---|---|---|
401 | Unauthorised | Fail the task |
403 | Access Denied | Fail the task - return an appropriate message |
500 | Internal server error | We will raise an error with the HTTP Reason as the Orchestra message |
Last updated