Forum Discussion
Intermittent Pipeline Failure with HTTP Timeout Error Referencing Logic App Limits
Intermittently, when executing our pipeline, we encounter the following error message:
"HTTP request failed: the server did not respond within the timeout limit. Please see logic app limits at https://aka.ms/logic-apps-limits-and-config#http-limits."
- No Logic App or similar service is explicitly invoked within the pipeline.
- The error occurs sporadically, approx once a month, and is not tied to a specific step or dataset.
- Timeout limit referenced appears to be related to Logic App HTTP connector limits, but this service is not part of our architecture.
Thanks in advance.
8 Replies
HI mstoegerer,
At the step where it fails, Enable retries on pipeline activities : Retry count as 3 to 5 and Retry interval as 30–120 seconds.Reduce parallelism where possible (For Each batch size or concurrent triggers).
Monitor capacity used for the pipeline activities. IF above steps does not resolve the issue, could you please share what is the step where it is failing and pipeline architecture .
Thank you.
This could very well be a timeout issue on the API side of things, not your side. We see it with the API of one of our suppliers, as mentioned: add a retry of 3 to 5 times with and interval of 30 seconds or so
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:
