Forum Discussion
InvalidHttpRequestToLivy: from cannot be less than 0 HTTP status code: 400
I haven't opened any support ticket. I was able to fix the issue by increasing the concurrency limit to 20 by which the execution time falls with in the session time out limit (28-29 mins).
Thanks for the support.
Hi zakeer1517,
Thank you for reaching out to the Microsoft Fabric Community, and thanks to Vinodh247, shared valuable inputs on this thread. The solution provided by the super user is correct and aligns well with the issue you are described.
Based on your detailed analysis and the consistent failure pattern, this does appear to be related to a possible Livy API limitation or bug, particularly given the error:
InvalidHttpRequestToLivy: from cannot be less than 0.
Since you've already tried increasing the session timeout and scaling up the capacity without success, I recommend raising a Microsoft Fabric support ticket. This will allow the engineering team to further investigate the backend Livy logs and session handling in detail. You can create a Microsoft support ticket using the link below: https://learn.microsoft.com/en-us/power-bi/support/create-support-ticket
In the meantime, consider reducing the concurrency level or breaking the workload into smaller DAG batches as a temporary workaround to help avoid the failure.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you for using Microsoft Community Forum.
Hi v-kpoloju-msft & Vinodh247
I tried reducing the concurrency level to two and ended up with the same error.
Hi zakeer1517,
Thanks for the follow up question. As I mentioned in my previous post, please consider raising a support ticket. This will allow the engineering team to investigate the backend Livy logs and session handling in detail.
Thank you for using the Microsoft Community Forum.
Hi zakeer1517,
We are following up once again regarding your query. Could you please confirm if the issue has been resolved through the support ticket with Microsoft?If the issue has been resolved, we kindly request you to share the resolution or key insights here to help others in the community. If we don’t hear back, we’ll go ahead and close this thread.
Should you need further assistance in the future, we encourage you to reach out via the Microsoft Fabric Community Forum and create a new thread. We’ll be happy to help.
Thank you for your understanding and participation.
I haven't opened any support ticket. I was able to fix the issue by increasing the concurrency limit to 20 by which the execution time falls with in the session time out limit (28-29 mins).
Thanks for the support.