在嵌套管道中任务的ADF管道故障 [英] ADF Pipeline Failure of a Task when in a nested pipeline

查看:84
本文介绍了在嵌套管道中任务的ADF管道故障的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们有一个嵌套的管道场景...... 3个管道(A,B,C)。  
$


管道A使用ForEach对结果进行查找和循环,调用适当的管道B


管道B确实使用ForEach查询和循环结果,调用适当的管道C


管道C也使用ForEach进行查找和循环结果。 在每个ForEach项目中,如果条件检查正在循环的项目。 有6种可能性。 所有如果条件以相同的方式运作。 真实条件
的支票;调用特定管道(管道D至I之一)以运行复制数据和其他内容,如果特定管道的结果调用FAIL,则调用逻辑应用程序将错误结果发送到电子邮件地址。 前5个调用完美地工作
...它完全符合我的说法...即使我有多个项目失败,它也能按照设计正确运行。
但是该集合的第6项(与其他项目完全相同)并不实际沿着FAILURE路径前进(当调试或从更高级别的管道触发时),即使特定的管道调用DOES正确失败。



特定场景:



  • 调用时管道C的触发模式或调试(直接)......它可以成功完全沿着故障路径向下移动而没有问题。



  • 在触发模式中调用或从管道B调用(调用管道C)...它成功地完全沿着失败路径向下移动而没有问题。



  • 在触发模式下调用或从管道A调用(调用管道B调用管道C)时......它无法成功沿着失败路径向下移动。 即使任务失败。


任何想法?

解决方案

您好rwezowicz并感谢您将此问题提请我们注意,但首先,你能帮我澄清几点吗?


当你说"管道B使用ForEach对结果进行查找和循环,调用适当的管道C"


你的意思是'ForEach '类型活动,有一个'执行管道'类型活动,

或,
你的意思是在'ForEach'活动'A'内存在'ForEach '活动'B'里面存在'ForEach'活动'C'?


We have a nested pipeline scenario ... 3 pipelines (A, B, C).  

Pipeline A does a lookup and loops on the results with ForEach which calls the appropriate Pipeline B

Pipeline B does a lookup and loops on the results with ForEach which calls the appropriate Pipeline C

Pipeline C does a lookup and loops on results with ForEach as well.  Within each ForEach item, If Conditionals check the items that are being looped on.  There are 6 possibilities.  All If Conditions operate the same way.  The True conditions of the check; Call a specific pipeline (one of Pipelines D thru I) to run Copy Data and other stuff, AND if the results of the specific pipeline call FAIL then call a Logic App to send the error results to an email address.  The first 5 of the calls work perfectly ... it does exactly what I stated ... even if I have multiple items fail, it does correctly operate as designed. BUT the 6th item of the set (set up exactly the same of the others) doesn't actual ever proceed down the FAILURE path (when debugged or triggered form a higher level pipeline), even though the specific pipeline call DOES correctly FAIL.

Specific Scenarios:

  • When called in Trigger Mode or Debug from Pipeline C (directly) ... it DOES successfully fully travel down the On Failure path without issue.

  • When called in Trigger Mode or Debug from Pipeline B (which calls Pipeline C) ... it DOES successfully fully travel down the On Failure path without issue.

  • When called in Trigger Mode or Debug from Pipeline A (which calls Pipeline B which calls Pipeline C) ... it DOES not successfully travel down the On Failure path.  Even though the task DOES fail.

Any ideas?

解决方案

Hello rwezowicz and thank you for bringing this issue to our attention, but first, could you please help me clarify a couple points?

When you say "Pipeline B does a lookup and loops on the results with ForEach which calls the appropriate Pipeline C"

do you mean that inside the 'ForEach' type activity, there is an 'Execute Pipeline' type activity,
or,
do you mean that inside the 'ForEach' activity 'A' there exists a 'ForEach' activity 'B' inside which exists a 'ForEach' activity 'C' ?


这篇关于在嵌套管道中任务的ADF管道故障的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆