This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 78%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESH%3C/text%3E%3C/svg%3E)
Whe running a copy activity in ADF, the copy runs fine and gets done with no errors. I see 5 files are skipped. These are "xlsx"files. The "skip incompatile rows" option is disable in my setttings.
This copy runs from Amazon S3 compatible storage system to Azure blob.
Any idea or suggestion will be highly appreciated.
Thanks in advance.
Can you please provide the copy activity source and sink configurations images? And what are the dataset types?
Is the source and sink dataset type as Binary?
And have you added any wild card path character?
And can you clarify what you mean by it skipped xlsx files? So does it mean there were other file types that were copied from source to sink but not the xlsx files
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 8%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EST%3C/text%3E%3C/svg%3E)
@Salomon Henriquez We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
When the Fault Tolerance feature is enabled in ADF, it skips rows that don't match the destination dataset schema.
Check the logs on Azure Blob Storage for incompatible rows to identify the cause of the failure. It seems the rows skipped in the first run were not corrected at the data source, causing them to be skipped again.