โ02-17-2021 10:30 AM
Hi, We have a pipeline which trigger another pipeline with the help of โTask Execute Snapโ and it stopped working for the last few days.
I was told that โTask Execute Snapโ has deprecated, we have tried to execute the pipeline with the help of โPipeline execute Snapโ but facing lot of Issues.
Could you please check and let me know that how do we effectively execute the pipeline inside pipeline.
Thanks in advance.
Gopi k
โ02-18-2021 12:33 AM
Hi,
After running close to 2hours of execution, the pipeline failed with the below error.
The Update statement is the one which update the status in the table for all the incoming documents.
I have not changed any other thing in the pipeline other than โExecute Pipeline Snapโ instead of โTask Execute Snapโ
Could you please share your thoughts if any.
Thanks.
โ02-18-2021 05:51 AM
You may need to read through the documentation on the Pipeline Execute snap as it isnโt exactly a replacement of the Task Execute.
https://docs-snaplogic.atlassian.net/wiki/spaces/SD/pages/1438684/Pipeline+Execute
The deadlock behavior you are experiencing is not related to the Pipeline Execute. This is a database deadlock, so it is related to how the update statement is being executed. You may wish to use โValidate Pipelineโ to view the documents as they are being passed to the child and determine if the child will process the records appropriately.
Also remember that by enabling โreuse executionsโ on the Pipeline Execute, the pipeline parameters passed to the child are only evaluated on the first document, which I believe is different from the Task Execute behavior.
โ02-19-2021 08:46 AM
Thanks for the information. I will validate it with my pipeline.
โ02-19-2021 09:11 AM
The combination of your posts:
and
indicates to me that the error is within your SQL Server and has nothing to do with the Task Execute being deprecated. I think the โdeadlock victimโ error needs to be evaluated first with your DBA or DBD before trying to fix the issue by pipeline modifications. Then move on to the Pipeline Execute after the DB error is fixed.
(note: I typed this up before I fully read Koryโs post, so it may be redundant; but I submitted anyway in case it helps)