Run job
Trigger a job in Render
Last updated
Trigger a job in Render
Last updated
Triggers and monitors a Render job using
Having Render as part of your stack is extremely powerful. As any application can be hosted in Render, this integration can be used to run any arbitrary code: python, javascript, or even Rust are all possibilities with the Render integration.
This is very similar to using . Data Teams typically use Render to run code that fetches data from a custom location for either ETL or ELT purposes.
There are a number of advantages to triggering jobs in Render in Orchestra vs. using their native scheduler:
Make use of Orchestra's advanced scheduler, which supports timezones and daylight savings time
Trigger and monitor multiple Render jobs in a single DAG
Trigger Render jobs alongside other services such as or
Gain end-to-end lineage across Render jobs and upstream tasks e.g. dbt Cloud Tasks
These parameters are required to run the Request Task
Task name
String
N.A.
Send Request
Start Command
Bash string
Should be executable by a Bash script
python run.py
Note: Orchestra will parse the logs from render to ensure that even if the build from Render succeeds but the underlying Tasks fail, the correct status code is shown in Orchestra so teams can be adequately alerted on accordingly.
Head to your Render dashboard and select the service you want to run.
In the URL, you will see the service ID. See image below:
Orchestra will fail the Task if the response code isn't a 2xx code.
401
Unauthorised
We will raise an error and parse the raw error message from the Render 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
Orchestra will use to trigger your job. Your startCommand should be the correct bash string to start your job. e.g.
