What type of address would result in an error code "5200" when executing a Finalist job

Products Affected:  Finalist
In Finalist, you can process an input file and for every address that we assign a +4, return the date the address was processed (using iprocess/oprocess fields and the process flag) in your output.  The next time you run Finalist, if we see that we already processed the record and assigned a +4 in a previous run, we will bypass that record.  By doing this, jobs will run faster as we are processing less records.  The only time you will see a 5200 error is when we have encountered a record that was previously assigned a +4.

5200 Information: Address bypassed counted correct in Process Unassign run.

Assign Unassign Records Indicate how to code previously unassigned or expired addresses. For more information on the assign/unassign feature, refer to the description of the cProcessUnassigned field of the PBFNSetupDef structure.
  •  OFF — Process all supplied addresses.
  •  ON — Process only previously unassigned or expired addresses. If an encrypted address assignment date (cProcessDate) in the  PBFNProcessDataDef structure is passed to Finalist and that assignment date meets USPS regulations for valid address records, Finalist will  not process that record but will include that record as valid for CASS record counts. If a record has not been previously coded and a date assigned,  Finalist will also process that record. Records bypassed and counted will return with a 5200 error code. This date must be stored and passed  on subsequent processing runs.
  •  XXX — Number of elapsed days since address was assigned. This number can be any value from 1 to the USPS determined number of days an address is valid. That value is currently set to 180. If a number greater than 180 is entered, the USPS expiration days are used.
  •  Blank — Defaults to OFF.
UPDATED:  August 31, 2017