When importing users/leads via CSV for tagging, if the import has more than 10 errors, we're unable to view the specific rows that caused those errors. This limits the ability to quickly identify and fix issues in bulk.
It would be better if we could export the rows that failed during import, ideally in a CSV format with error details per row. We could then:
- Review exactly which users/data rows failed and why.
- Correct the issues in the exported file, or add more data for more accurate mapping.
- Re-import the corrected file to complete the process.