Thank you very much for the detailed response! We unfortunately can't proceed with option 1, as we do require multiple places that can trigger the pipeline (an API call to the parent job, and a direct API call to the pipeline itself). This is due to the specific configurable options available in a pipeline API call vs a job API call, namely `full_refresh_selection` to fully refresh specific tables. 

We do have queue enabled at the job level and a small `max_retries` on the pipeline.

For now it seems we will need to open a ticket and wait until the pipeline execution queue is fully rolled out.