Understand repeated SFTP filenames in the school data importer

Reusing a filename

In the school-level data-importer SFTP flow, the scanner looks for CSV files currently in the school's import folder. It creates an import for the selected file, matches its filename to an import configuration, and removes the source object after copying it. This flow does not reject a new upload solely because a previous import had the same filename.

Re-uploading changed data with the same valid filename can therefore create another import after the earlier source file has been processed. Confirm the new entry and its row results in import history. Do not equate the upload completing with all rows importing successfully.

What to check

Confirm the CSV extension, destination folder, filename/configuration match, upload time, and the new import's status. An unrecognized filename can produce a failed import. Schools using preprocessing have additional processing stages, so the appearance of the import need not be immediate.

Avoid overwriting a file that is still awaiting pickup or processing; the code review does not guarantee that two rapid uploads at one path both become separate imports. This guidance is specific to the school-level data importer, not every legacy volunteer-management SFTP workflow.