Loading

Marketing Cloud - Error: 'Import Failed' during Import Activity

Data da publicação: Nov 21, 2025
Descrição
In some scenarios an error message may be received within an Import notification after an Import completes.   Sometimes this message may contain a specific type of error that seems general but actually points to a specific problem with data format/Data Extension format/provisioning.   
Resolução
Error TextMeaningSuggested Action
Import Failed: For more information on why the data could not be imported review your notification email or click "Retry" to retry the import.This is the most generic of the Import Failed errors. Use the notification email for more information about the cause of the error. 
  • Verify that a FTP User has been configured within the Setup Application.
Import failed: File {{filename}} not foundThe source file that the activity expected to find is missing, or no file matching the file naming pattern was found. 
  • Verify that the file pattern of the file matches the pattern configured in the Import File activity.
  • Verify that the file was added to the import location as intended, especially if files are dropped by an automated process. 
  • Verify that the correct File Location was used in the import activity. 
    Example: If the file is located at Triggered_Automation\Folder A and if the 'File Location' used in the activity is anything other than relative folder location type, the import will fail.
  • Ensure file name does not contain over 100 characters
Import failed: Invalid file ageThe timestamp on the file is invalid or settings in the configuration of the activity prevent files of a specified age from being processed. Ensure that the file is not older than the defined age limit setting or modify the age limit setting.
Import failed: Invalid file sourceFile source is invalid.Enter a valid file source.
Import failed: File location invalidFile location is invalid.  Enter a valid file location.
Import failed due to system errorThis typically is an error that indicates an intermittent failure has occurred or that an import falls into a bucket that does not have a generic error message.  Retry the Import to see if this was a temporary issue.

Quickly review the file to see that there are not any odd formatting problems that immediately stand out which might cause delimiter problems causing the file not to be read properly.
Import failed due to "Empty Source" errorThe import file has no data

Find the import file used in the activity on the account's ftp to confirm that it is empty.  This can also occur due to the file being formatted incorrectly. 

Import failed: "Invalid Date"The import file has a date field with a format that does not match the date format selected for the accountWhen you import dates into lists or a data extension, the date must be in the same format as is indicated on your account. If your user date format is different from the account, you must still use the format of the account. 
Import Failed: InvalidFieldMapThe headers on the Import file doesn’t match the Field-name on the Data Extension.The solution is either to map the fields manually or to ensure that field names and header rows match exactly.
Not all streams reached the end of their file.Import Options Respect double quotes ( " ) as a text delimiter is selected in Import configuration and there is a field that does not have a closing ".Ensure all fields with opening " have a closing " as to not cause delimiter issues.
Source List files are limited to 0.5 MB (500 KB). Please try again with a smaller file.The import file is too large to be processed as a source file.A new file should be created or the header and the header row from the old file as well as a single row of data should be added.    This will avoid data size problems that occur while the information is being transferred through a browser window.
No valid data found in input. One or more errors indicating why the import was aborted may be logged to the dbo.ImportError table.A delimiter issue exists so the number of total columns mapped by the import may not align correctly with the way that the data in the Data Extension.Check to see if there are more delimiters per row in columns that are mapped.  This typically occurs when a delimiter is contained in a row of data which throws off delimiter location for the file.   
Invalid Field CountA delimiter might exist that throws off the ordinal or number of fields within an Import.Select the option to "Respect double quotes as a text qualifier".
DecompressionTooManyFilesThis happens when 2 files are both in the same zip folder and importing the ZIP file.Ensure that only one file is placed in the .zip file.
ValidationResultCode:LineReaderBufferOverFlow.Follow this. MC INTERNAL: Import Error: validationResultCode: LineReaderBufferOverFlow
Número do artigo do Knowledge

000384219

 
Carregando
Salesforce Help | Article