This should happen rarely, if ever, in a correctly functioning system, so I'm fine with every time.  It does occur to me that if we have a node failure during CSV loading, that strange and potentially bad things might happen (in some cases we return a 'result unknown' code which will also be != ClientResponse.SUCCESS, which means we might end up trying to insert rows twice, ugh).