What causes DF-Executor-InternalServerError?

A transient ADF service issue in your Azure region — Spark cluster provisioning failed or the job submission layer encountered an internal error. An Azure infrastructure incident affecting the ADF Mapping Data Flows service in the region. A transient storage or networking issue in ADF's internal infrastructure that prevented the data flow job from starting or completing. An ADF service deployment caused a brief period of internal errors (rare but possible during rolling updates)

How do I fix DF-Executor-InternalServerError?

Retry the pipeline — internal server errors are often transient Spark cluster or ADF service issues that resolve on the next run.. Check the Azure Service Health dashboard for active incidents in the ADF region that may be causing transient failures.. Review the ADF activity run output for any additional sub-error codes that indicate a more specific root cause.. If the error is persistent and not transient, enable debug mode to reproduce it interactively and isolate the failing transformation step.. Open a support ticket with Microsoft if the error persists across multiple retries with no apparent configuration issue.

Medium severitydata flow

Power BI Refresh Error:
DF-Executor-InternalServerError

What does this error mean?

The ADF Mapping Data Flow service encountered an unexpected internal error in the execution layer. It may also indicate a temporary ADF service incident in your Azure region.

Common causes

1A transient ADF service issue in your Azure region — Spark cluster provisioning failed or the job submission layer encountered an internal error
2An Azure infrastructure incident affecting the ADF Mapping Data Flows service in the region
3A transient storage or networking issue in ADF's internal infrastructure that prevented the data flow job from starting or completing
4An ADF service deployment caused a brief period of internal errors (rare but possible during rolling updates)

How to fix it

1Retry the pipeline — internal server errors are often transient Spark cluster or ADF service issues that resolve on the next run.
2Check the Azure Service Health dashboard for active incidents in the ADF region that may be causing transient failures.
3Review the ADF activity run output for any additional sub-error codes that indicate a more specific root cause.
4If the error is persistent and not transient, enable debug mode to reproduce it interactively and isolate the failing transformation step.
5Open a support ticket with Microsoft if the error persists across multiple retries with no apparent configuration issue.

Frequently asked questions

How do I check whether there is an active ADF service incident?

In the Azure portal, search 'Service Health', filter by subscription and region, and select Azure Data Factory. Subscribe to ADF incident alerts to be notified automatically.

Is there anything in my pipeline configuration I should check after an InternalServerError?

Usually no — this is a server-side error, though it can co-occur with a configuration issue. If the error persists after retrying, enable debug mode to check if it reproduces interactively.

How many times should I retry before opening a support ticket?

Retry 2-3 times with at least a 5-minute gap. If all retries fail and no ADF service incident is active for your region, open a support ticket with the activity run ID.

Will downstream Power BI datasets be affected?

Yes — the pipeline fails and the target table receives no new data. If the retry succeeds, downstream datasets will catch up on the next run.

Official documentation: https://learn.microsoft.com/en-us/azure/data-factory/data-flow-troubleshoot-guide