Forum Discussion
Intermittent Pipeline Failure with HTTP Timeout Error Referencing Logic App Limits
Hi smeetsh & v-saisrao-msft ,
thanks for your replies.
We have already considered a solution using retries. However, the underlying pipeline is quite large, and sometimes errors occur there that cannot be resolved by a retry. That’s why we don’t really want to implement a retry in this case. What would be most interesting for us is to understand why this error occurs in the first place.
Hi mstoegerer ,
Since we don’t have visibility into the backend logs required to investigate this further, we won’t be able to analyze the root cause from here.
Please submit a Microsoft support ticket using the link below and include the affected pipeline run IDs, timestamps, and region. The support team will be able to review the internal logs and assist in identifying the underlying cause.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn
Thank you.
I think you replied to the wrong person 😂
Another option you can try is to make sure there is no paralelism, and to make the time out value higher? Below is what one of ours looks like, also upping the request interval may help. Some API's do not like it when you fire to many requests to quickly..
There is no paralellism or anything. Just one pipeline calling another pipeline:
HI mstoegerer what is the pipeline you are calling like? The error is the pipeline being called, not the activity that calls the pipeline
