Forum Discussion
Failed to create Livy session for executing notebook. Error: [BadGateway] The request for workload '
Hi UdaySutar ,
Thank you for reaching out to the Microsoft fabric community forum. Also thank you jennratten for your inputs.
The error “Failed to create Livy session... [BadGateway]” with HTTP status code 502 typically indicates that the Spark runtime couldn’t start due to capacity issues or a transient service error. This may occur if the Spark pool (capacity ‘AA19707D’) was paused, deallocated, or under heavy load at the time of execution.
Please check the Notebook run logs in Synapse or Microsoft Fabric/ADF for more details. Ensure the Spark pool is active, and your workspace has access to available capacity. If you're using Microsoft Fabric, review the Capacity Metrics App to confirm there are sufficient resources (CPU, memory, concurrency).
We also recommend setting a retry policy and increasing the timeout in the pipeline activity to handle transient failures. Let us know if the issue persists after these checks.
I hope this will resolve your issue, if you need any further assistance, feel free to reach out.
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.
Thankyou.
Hi UdaySutar ,
Thank you for reaching out to the Microsoft fabric community forum. Also thank you jennratten for your inputs.
The error “Failed to create Livy session... [BadGateway]” with HTTP status code 502 typically indicates that the Spark runtime couldn’t start due to capacity issues or a transient service error. This may occur if the Spark pool (capacity ‘AA19707D’) was paused, deallocated, or under heavy load at the time of execution.
Please check the Notebook run logs in Synapse or Microsoft Fabric/ADF for more details. Ensure the Spark pool is active, and your workspace has access to available capacity. If you're using Microsoft Fabric, review the Capacity Metrics App to confirm there are sufficient resources (CPU, memory, concurrency).
We also recommend setting a retry policy and increasing the timeout in the pipeline activity to handle transient failures. Let us know if the issue persists after these checks.
I hope this will resolve your issue, if you need any further assistance, feel free to reach out.
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.
Thankyou.
Hi UdaySutar ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.