Thanks Phil, that CSV validator link is a great resource.
I did extra data cleaning: removed commas, ampersands, qoutes, double qoutes and stripped text in all columns. I was able to create a CSV that passed the validator test.
But am still having the same issues on the Survey123 web browser when editing the submitted data. Error message is still the same as the initial screenshot that I sent. So maybe its a performance issue on the web browser side due to the size of the CSV file (can't do anything about it since I already deleted all unnecessary columns on the table and will need all rows).
I was pleasantly surprised that the pulldata is really fast on the mobile app. I am using both passing information from Collector and pulldata from the 32 MB CSV, satisfied with the speed so far.
Another question, is there a way to disable the pulldata from CSV on the web browser side? Since, once the data is submitted from the field, the pulldata part is really not needed on the office backend, they only need to be able to edit/update the data and ability to edit the photo attachments (I know this could be done in different ways in AGOL, but based on user feedback in the organization, they like the form-view panel as an editing interface).