What causes Fabric Copy Activity Error 20746?

The 'invalidFileName' skipErrorFile setting was configured on a source connector that does not support it. A copy activity payload was cloned from a compatible pipeline and applied to an incompatible source connector. Manual or template-based pipeline authoring incorrectly included skipErrorFile options for unsupported connectors

How do I fix Fabric Copy Activity Error 20746?

Step 1: Open the copy activity in your Fabric Data Factory pipeline editor and navigate to the Settings tab.. Step 2: Locate the 'skipErrorFile' configuration block in the source settings or advanced JSON payload.. Step 3: Remove the 'invalidFileName' property from the skipErrorFile object entirely.. Step 4: Save and republish the pipeline, then re-trigger the copy activity to verify the error is resolved.. Step 5: If skip-on-invalid-filename behavior is required, consider switching to a supported connector or handling file name validation upstream.

Medium severityconfigurationMicrosoft Fabric →

Power BI Refresh Error:
Fabric Copy Activity Error 20746

What does this error mean?

The 'invalidFileName' option in skipErrorFile is not supported for the specified source connector. This setting must be removed from the copy activity payload.

Common causes

1The 'invalidFileName' skipErrorFile setting was configured on a source connector that does not support it
2A copy activity payload was cloned from a compatible pipeline and applied to an incompatible source connector
3Manual or template-based pipeline authoring incorrectly included skipErrorFile options for unsupported connectors

How to fix it

1Step 1: Open the copy activity in your Fabric Data Factory pipeline editor and navigate to the Settings tab.
2Step 2: Locate the 'skipErrorFile' configuration block in the source settings or advanced JSON payload.
3Step 3: Remove the 'invalidFileName' property from the skipErrorFile object entirely.
4Step 4: Save and republish the pipeline, then re-trigger the copy activity to verify the error is resolved.
5Step 5: If skip-on-invalid-filename behavior is required, consider switching to a supported connector or handling file name validation upstream.

Frequently asked questions

Which connectors support the 'invalidFileName' skipErrorFile option?

Only connectors that support direct binary copy with folder-level operations support 'invalidFileName' in skipErrorFile. Check the Microsoft Fabric connector-specific documentation to confirm support before adding this setting.

Can I keep skipErrorFile configured but just remove invalidFileName?

Yes. You can retain other supported skipErrorFile options such as 'fileMissing' while removing the unsupported 'invalidFileName' key, as long as the remaining options are supported by your source connector.