Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount.
Register nowGet certified as a Fabric Data Engineer: Check your eligibility for a 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700. Get started
I have observed this behavior:
Pipeline A calls Pipeline B and Pipeline B calls Dataflow 1. Dataflow 1 is set to auto retry refreshing once in case of failure. Dataflow 1 retries and succeeds but Pipeline A sees two failures associated with Dataflow 1, thereby stopping the run with a failed status.
1. Is Pipeline A supposed to see that Dataflow 1 did succeed upon retry?
2. Is the presence of Pipeline B preventing Pipeline A from seeing the successful retry?
3. Is this a bug waiting to be addressed?
Appreciate the feedback from the community. Thanks!
Hi @ebjim ,
In your case, Pipeline A sees two failures, which indicates that the retry success was not propagated correctly to the parent pipeline. Please check if Pipeline A is configured to handle retry states from nested pipelines or data streams.
Alternatively, if the issue persists, try Azure Functions to orchestrate the pipeline and handle retries more robustly.
Best Regards,
Adamk Kong
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
If you love stickers, then you will definitely want to check out our Community Sticker Challenge!
User | Count |
---|---|
8 | |
2 | |
2 | |
1 | |
1 |