If there is a limit on the size of the config file used to identify automated traffic, then the process for updating it needs to save the updated file in temporary storage and sanity-check it; if it fails the sanity check, it should throw an error and reject the update. If it passes the sanity check, the old file should be backed up, and only then should the updated file be moved to replace the old one. That way, if there's an identifiably out-of-band update, it doesn't stomp on the current good data, and even if it passes the initial check, the previous iteration of the file is immediately recoverable to restore service. And there should be a utility that copies -- not moves -- the backup file back to the main file.