This article explains steps you can take to investigate issues with tasks that have a method of Collect or Download.

Investigating Collect QA Issues

1. If a problem with lead files we loaded, review the files we loaded in Data Archive
   1. If the file is still in Insyncing Data Drop:
      1. Check Slack channel #sales-leads-processing for errors
      2. Ask Ops Specialist to check Jobs server logs for preprocessing errors
   2. Make sure all data is there:
      1. no missing days (a full range of dates)
      2. no missing columns
      3. data is populated in all columns (not blank)
   3. See Master Clarivoy Data Input Requirements for general column requirements, then check Vendor Details & Instructions board for vendor specific columns
   4. Make sure all data in the rows line up with the column headers
   5. Occasionally an improperly formatted CSV file (due to a vendor system issue) may cause data to line up incorrectly.
   6. CSV files can be generated or saved improperly by some systems/users. If you open Excel and see a message in a cream colored bar at the top of the sheet referencing the data being in .TXT format, resave the file using Save As and select CSV UTF-8 (Comma delimited) (.CSV) as the file format.
2. You may need to pull a new file if the data was not pulled correctly the first time. If this is the case, let the Ops Specialist know to delete out the old file from the database first.
   See also:
   1. Deleting a Sales File
   2. Deleting a Leads File
3. If you see this error in the preprocessing error log:
   ERROR 4122056 : field larger than field limit (131072)
   the contents of one cell has exceeded the max field size for a .CSV file. Resave the file as a .XLSX
4. If it is a new vendor, ask Ops Specialist to verify it is mapped correctly.
   See also:
   1. Mapping Leads Files
   2. Mapping Sales Files 
   3. Mapping Multi Files