Native ImportCSV Bug?

[JMPeterson]

Running into an interesting bug lately. We use the native ImportCSV function, and are starting to see duplicate entries in the database for a single import.

I have not been able to see duplicate runs in the logs, but the DB clearly shows the same rows being imported at least twice. The only difference I can see between the rows of data, are the timestamps. Normally there is a small fraction of a second difference between the imported rows (see orange highlighted), but in this case its like the import function is being engaged multiple times in a second.

The users can not act fast enough to hit the import button, clear the pop-up and re-engage the import process in the four tenths of a second discrepancy between these entries. And there are only a dozen rows on the import, which would be processed almost immediately. Does the CSV import have an auto-retry function like a bot? Are we somehow sending the same data down two separate data-streams simultaneously?

Has anyone else seen any odd behavior with CSV imports?

[SkrOYC]

Actually is not clear to me what is going on on the UX side of things.

I know that Export works without giving the "OK" when the action button is clicked, but for Import it works just after you select the file. In which sense you feel like there is an automated process that you can't control? Could you record the behavior and post it here as a gif?