Bug? Parameterization of the orchestration name for the "Run Orchestration" component doesn't work inside a shared job

Matillion ETL
1
  • In my main orchestration, I have a "Run Orchstration" component. The orchstration that should be executed by this component can be set via variable, and additional parameters can be provided via the "Set scalar variables" property.
  • However, when I create a shared job from my main orchestration, I cannot successfully excute the shared job (error message: "Parameter validation failure: Job Name - could not find job with name [Print_The_Values]"). However, the orchestration "Print_The_Values" exists.
  • Is this a bug in Matillion?
2

Hi JD832544,

 

Confirming that I find the same as you, and I agree I think it's a bug. I tried on Matillion ETL for Snowflake on AWS version 1.53.

 

Steps to reproduce:

 

  • Create an Orchestration Job
  • Use Manage Job Variables to add a parameter, named jv_jobname
  • Add a Run Orchestration component, and in the Orchestration Job parameter: tick Use Variable and set its value to ${jv_jobname}
  • Generate a Shared Job from it, using the right-click context menu in the job tree
  • Pull the newly created Shared Job onto the canvas of a different Orchestration Job
  • Set its parameter to the name of an existing Orchestration Job
  • Whenever you try to run it, it always fails with "Parameter Validation Failure" error, regardless of whether or not the parameter points to an existing job

 

Has anybody in the community managed to get this to work, or know a workaround?

 

Ian

 

3

Hello Ian, thanks for confirming it as a bug. I am facing it using Matillion Redshift 1.53.10

4

Hi JD832544,

 

I have some more information on this... I checked this internally, and found that it was done by design.

 

From within a Shared Job it's impossible to call an Orchestration Job that was not packaged as part of that Shared Job. Basically that means you can't use a parameterized Run Orchestration component inside a Shared Job.

 

As it was a deliberate design choice to work that way, my suggestion is to raise it on our Ideas Portal with a little detail on your use-case. That way others can see it and potentially upvote.

 

Best regards,

Ian

 

5

Hi All,

 

We have a similar situation where we need to do a set of validation checks before executing an Orchestration job. These checks are to be applied for every job in Schedule. The ideal solution would be a Shared Job component triggering an Orchestration job , which is passed via parameters.

 

Seems like Shared jobs aren't allowed to run Orchestration jobs out of its package by Design. Would love this design to be updated to allow execution of Orchestration jobs outside of the package

 

Not sure if there is an idea raised for this problem, as I was not able to find one.

 

Raised an idea here , can you please upvote so that it gets enough traction.

 

https://matillioncommunity.discourse.group/t/bug-parameterization-of-the-orchestration-name-for-the-run-orchestration-component-doesnt-work-inside-a-shared-job/1338

 

Cheers,

Anu

6

Sorry an incorrect link above. Here is the link for idea to upvote.

 

Idea: Allow Shared Jobs to Run Orchestration jobs which are not packaged as part of Shared Job (matillion.com)