Hello @Sofía Neithardt ,
Welcome to the Microsoft Q&A forum.
When the Fault Tolerance feature is enabled, it skips rows that don't match the schema of the destination dataset. In your case, the semicolon delimiter is causing some rows to have more columns than the correct ones, which is why they are being skipped.
Did you examine the logs on the Azure blob storage (incompatible rows) to see the cause of the failure?
It seems like the rows skipped in the first run were not fixed in the data source, which caused them to be skipped again in the second run. Please check the log files to see if this is the case.
Also, you can try to handle the semicolon delimiter issue by using the correct delimiter settings on the source dataset.
Reference document:
I hope this helps. Please let me know if you have any further questions.