Data flow error: 4501 - related to WranglingDataFlow

Michael S 1 Reputation point
2020-06-04T13:26:01.637+00:00

Hi guys,

Please, for some reason, I'm getting this error message when I try to debug a pipeline with a wrangling data flow activity.

{
    "errorCode": "4501",
    "message": "Failed to fetch execution state: '', please retry. If the problem persists, please contact Azure Support",
    "failureType": "UserError",
    "target": "WranglingDataFlow",
    "details": []
}

I've searched everywhere online and the closest post I found was this.

Can I confirm that the solution here would work for me? i.e. increasing cluster size.
If yes, is there some way I could restart something to resolve the heap space issue? As increasing the overall cost of the service might be a tough sell for the employer.

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.
4,671 questions
Azure Data Factory
Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
10,133 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. KranthiPakala-MSFT 46,442 Reputation points Microsoft Employee
    2020-06-04T17:26:31.327+00:00

    Hi All,

    Apologies for the inconvenience caused. This issue is a result of underlying Outage related to Azure Resource Manager (ARM) as called out by @Cedersved . Thank you so much @Cedersved for pitching in and calling out.

    Here is the latest update from status page: (Please follow this page for further updates: https://status.azure.com/en-us/status)

    Warning: Azure Resource Manager (ARM) - Active

    Starting at 08:45 UTC on 04 Jun 2020, a subset of customers may experience issues with resource creation for services that depend on the Azure Resource Manager (ARM) platform.

    We have identified a fix for an underlying networking issue, and have deployed this fix to all impacted regions. Customers may see recovery in most regions as we continue to validate mitigation. The next update will be provided in 60 minutes, or as events warrant.
    This message was last updated at 16:11 UTC on 04 June 2020