What causes DF-Executor-UserError?

A Derived Column or filter expression references a column that no longer exists in the incoming stream — the source schema changed and the expression was not updated. A cast or conversion expression receives a value that cannot be converted — for example, toInteger() called on a column that contains non-numeric strings. A function is called with an incorrect argument type or an unsupported argument count — ADF expression function signatures are strict. A sink column mapping references a column name that does not exist in the incoming data stream after recent transformation changes

How do I fix DF-Executor-UserError?

Read the full error message in the ADF activity run output — DF-Executor-UserError is a wrapper; the inner message names the specific transformation, column, or expression that failed.. Open the data flow in ADF Studio and go to transformation named in the error message — inspect the expression or configuration that references the failing column.. Enable Debug mode and use 'Data preview' on the failing transformation step to reproduce the error interactively with live data and see the exact row and value that caused it.. If the error references a column that no longer exists in the source, refresh the source schema by clicking 'Import projection' in the Source transformation settings.. Check data type mismatches — if a Derived Column or Cast expression receives a value that cannot be converted (e.g., a non-numeric string passed to toInteger()), add an iif(isNan(value), null, toInteger(value)) guard.

Medium severitydata flow

Power BI Refresh Error:
DF-Executor-UserError

What does this error mean?

A data flow transformation failed due to a user-configuration error — an invalid expression, missing column reference, unsupported function argument, or incompatible data type in the transformation logic. DF-Executor-UserError is a wrapper code; the inner error message identifies the specific transformation and the root cause.

Common causes

1A Derived Column or filter expression references a column that no longer exists in the incoming stream — the source schema changed and the expression was not updated
2A cast or conversion expression receives a value that cannot be converted — for example, toInteger() called on a column that contains non-numeric strings
3A function is called with an incorrect argument type or an unsupported argument count — ADF expression function signatures are strict
4A sink column mapping references a column name that does not exist in the incoming data stream after recent transformation changes

How to fix it

1Read the full error message in the ADF activity run output — DF-Executor-UserError is a wrapper; the inner message names the specific transformation, column, or expression that failed.
2Open the data flow in ADF Studio and go to transformation named in the error message — inspect the expression or configuration that references the failing column.
3Enable Debug mode and use 'Data preview' on the failing transformation step to reproduce the error interactively with live data and see the exact row and value that caused it.
4If the error references a column that no longer exists in the source, refresh the source schema by clicking 'Import projection' in the Source transformation settings.
5Check data type mismatches — if a Derived Column or Cast expression receives a value that cannot be converted (e.g., a non-numeric string passed to toInteger()), add an iif(isNan(value), null, toInteger(value)) guard.

Frequently asked questions

How do I find the actual cause inside a UserError?

In ADF Monitor, click the failed activity then 'Details'. The 'message' field names the specific transformation or column — the error code alone is not sufficient.

UserError appears on every run but the data flow worked before — what changed?

UserError surfaces after a data flow change, source schema update, or new column from the source. Check change history for recent edits — most commonly a renamed or removed column breaks downstream expressions.

How do I reproduce the error without running the full pipeline?

Enable debug mode and use Data Preview on each transformation step — UserError appears in the preview with the exact row and value that triggered it.

Will downstream Power BI datasets be affected?

Yes — the data flow fails and no data reaches the target. Dependent datasets and reports serve stale figures until the expression or configuration error is corrected.

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