Context parameter ignored during execution by TAC

[JQuinto1674574802]

The context parameter value of a job task is sometimes ignored during the execution. I consider this a bug because it does not always happen and can happen on any random job task.

To be more precise, the context parameter is taken into account, but its value is not.

Below, we can see a successful run of a job task where the context parameter "templateFilePath" has the correct value :

 

However, in the image below, we can see that during the execution of this task, the context parameter "templateFilePath" does not have a value :

 

This happens randomly for any job task and any context parameter.

Note : So far, I noticed that it happens only when we use custom values for a context parameter, and yes it is necessary that we use custom values for our jobs.

 

Between the two executions there has been no modification of the context parameter values, job artifact and other settings regarding the job task.

When re-running the job task after noticing the missing value, the value "magically" reappears.

Any help or suggestion would be greatly appreciated.

John Michael

[Anonymous]

Hi John,

It is very difficult to identify what is happening from the screenshots and not seeing the job or the flow (end to end). This *could* be a bug, but I am inclined to think that this is more likely due to something that I am not able to see here. I am of course happy to be proven wrong, since finding and fixing bugs only makes the software better 😉

Could I ask that you raise a support call about this? They will be able to go through this with you to see the issue in more detail and either help you find the issue or identify the bug.

Regards

Richard

[JQuinto1674574802]

Hi Richard,

Thanks for your reply! We develop jobs in the Talend Studio and publish them in the TAC (Talend Administration Center) server. The TAC helps us schedule jobs to run at certain times manage the frequency, keep track of all running jobs, view their logs, and much more.

Here is a view of the TAC platform (sorry for all the hidden information, although they do not matter in the resolution of this bug). We can see the selected job task "COMPLIANCE_Compliance_Monitoring" which contains the job developed in the studio and its context parameters (lower part of the image) :

 

As you can see, we have used custom values for this job task instead of the original and the parameter "templateFilePath" has our custom value applied to it.

The first 2 images I have shown in my original post are the job task execution details for 2 different executions at 2 different times. Both job tasks have been executed by the TAC at the times we have scheduled.

The problem lies here, the first execution contains the context parameter value "templateFilePath", but the second one does not (as if the TAC forgot to apply the value). When we noticed the missing value, we checked the context parameters and found that the the value of "templateFilePath" was indeed set. After running the job task again, without modifying anything, the context parameter value in "templateFilePath" magically appeared as mentioned before.

I will raise a support call about this and come back with answers if I can. In the meantime, I invite anyone having similar issues to like this post at the very least, to be sure that I am not the only one having this problem.

Best Regards

John Michael

[Anonymous]

Thanks for extra detail @John Michael Quinto​. When you speak to Support point them to this post so that you don't have to reiterate absolutely everything in the case. Also, request a Zoom meeting so that you can show them precisely what you are seeing. This will help them get a quick understanding of the issue and they will be able to dig into this more effectively than I can via screenshots and messages.

[JQuinto1674574802]

Thanks for everything, Richard! I will do exactly what you said and hopefully get back on this issue with a solution.