Random internal server errors: Cluster creation failed due to unexpected error

Rhuan Samary Barreto 95 Reputation points
2023-10-18T07:53:31.8633333+00:00

I keep getting this error in random pipelines I'm running. How can I retry it automatically?

{
    "errorCode": "145",
    "message": "Internal Server Error in Synapse batch operation: 'Cluster creation failed due to unexpected error. Please retry.'.",
    "failureType": "SystemError",
    "target": "FactWvActivity",
    "details": []
}
Azure Synapse Analytics
Azure Synapse Analytics
An Azure analytics service that brings together data integration, enterprise data warehousing, and big data analytics. Previously known as Azure SQL Data Warehouse.
5,350 questions
{count} votes

Accepted answer
  1. Bhargava-MSFT 31,251 Reputation points Microsoft Employee Moderator
    2023-10-24T16:09:39.9533333+00:00

    Hello Rhuan Samary Barreto,

    This issue has been mitigated, so you should not see these errors anymore.

    Please let us know if you still encounter any internal server errors.

    I hope this helps.


2 additional answers

Sort by: Most helpful
  1. Kleber Rebello 0 Reputation points
    2025-02-24T15:17:27.13+00:00

    Hi, there. I am seeing the same error from my dataflow. It does not look like the mitigation you applied worked.


  2. Shans Bloye 0 Reputation points
    2025-05-29T11:52:01.2333333+00:00

    This has reoccurred today for the Azure East US region, the issue is flagged in the Azure Service Health Monitoring Tool: https://azure.microsoft.com/en-us/get-started/azure-portal/service-health

    The current incident PT10-5VZ (Issues executing spark jobs for Azure Synapse Analytics in East US) is linked to Azure Synapse Analytics, however there is a clear link to ADF Mapping Data Flows which also run on the Spark Clusters.

    Not so much a solution but worth checking for Service Health events if you see similar error.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.