This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(262.40000000000003, 49%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESA%3C/text%3E%3C/svg%3E)
I have pipeline which created based on metadata driven and it has three properties. When i execute the pipeline using "Debug" or "Manual Trigger" it execute complete pipeline end to end but it comes to scheduled trigger it shows the pipeline status as completed but not execute completely. The manual trigger/Debug took 1 hour to load 20 plus tables however scheduled trigger complete less than 1 minutes and no errors at all.
what are other parameters it will search while use schedule trigger?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 12%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESV%3C/text%3E%3C/svg%3E)
Are you checking for some logic that prevents the pipeline from executing end to end ? Like some parameter value or something.
Could you please post your pipeline design? So that we can analyse the issue bettrr?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(172.8, 70%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
Hello @Sreenivas Amieineni , @Subashri Vasudevan ,
Please help me understand the situation fully.
it shows the pipeline status as completed but not execute completely
So you are saying in the monitoring view you see pipeline success , but when you look at the pipeline execution details it is still in progress? Like below pictures
I can't think of what would allow this particular combination. I'd have to give you a support ticket so we can investigate.
Or did you mean the trigger completed but the pipeline is still running like below pictures?
In this case you need to remember that trigger means the action which causes the pipeline to start. If a trigger fails, the pipeline does not start. The completion of a trigger is independent of the completion of pipeline run. A pipeline run can continue after the trigger run completes.
Before jumping into the suggestion of child pipeline completing but parent pipeline not continuing, I would like to ascertain what precisely is stuck. An activity run or pipeline run.
Hello @Subashri Vasudevan
There is no such logic to prevent pipeline execution and the same executed with "Debug" option or Manual Trigger. Given below the high level pipeline.
I now see that the first activity is execute pipeline. I saw a thread mentioning about the control not being returned to parent pipeline after child pipeline is done.
May be this is a bug.
@MartinJaffer-MSFT FYKI , could you please check this and let us know if we have this big with execute pipeline activity ?
Hello @MartinJaffer-MSFT , @Subashri Vasudevan
You can see below pipeline run and i don't see any "in progress" state of pipeline.
And Activity runs shows as completed
Trigger shows as completed.
This shows across all Pipeline/ Activity/ Trigger as completed but for each loop not loaded into BLOB storage using "Scheduled Trigger" where as "Manual trigger" perform as expected.
Thanks,
Sreenivas Amirineni
@MartinJaffer-MSFT did you get a chance to look into my question? i am still having the same issue with different azure accounts. The pipeline runs smooth with manual trigger but not with scheduled trigger? i am using meta data driven copy task and all parameters are good to pass.
@MartinJaffer-MSFT I found the issue is coming from ADF pipeline unable to connect to on premise sql server hence it return 0 records via bulk load activity? any suggestions over what are IP ranges that need to whitelist for on premise sql server?