Error Logging

There are two types of errors that might occur in processing these files: File processing errors and record processing errors. These errors are logged as follows.

File Processing Errors

There are various conditions that will cause the overall utility to fail and not process any records. These include an invalid tenant, invalid file format/path/name, incorrect userID and password etc. Also, the field identifiers in the input file might be incorrect and thus none of the records can be processed. These types of errors are logged into the File Processing Results log file.

The naming convention for this file is FileProcessing.inputfilename.log.

Two examples of these errors are as follows:

At: 2009-12-22 08:53:05

Error processing TestFile.csv: Login failure: Login name/password not recognized.

At: 2009-12-22 09:11:03

Error processing TestFile.csv: Line 1: Invalid column headers: unknown field specified: interaction-AmountDuee

As shown above, the log file is appended with each additional error.

Record Processing Errors

Record processing errors are divided into two categories: Contact Import Errors and Agent Email Errors.

Contact Import Errors – If records within the input file can’t be processed because of errors relating to the contact create or update process, details of those errors will be written to a contact import errors log file. This file will include the row# for each error, along with a description of the error. This file will ONLY contain error records.

The naming convention for this file is ContactImportErrors.inputfilename.log.

Agent Email Errors

If records within the input file passed the contact validation but did not pass the interaction creation validation, they will be written to the agent email error log. This file will include the row number of the record along with the error reason, and will ONLY contain error records.

The naming convention for this file is AgentEmailErrors.inputfilename.log.