Reprocessing Failed Records

D&B reprocessing is an automated way to reprocess those organization records that were sent to D&B for match and append or recertification, but the D&B connector could not process them successfully.

D&B (Dun and Bradstreet) reprocessing is an automated way to reprocess those organization records that were sent to D&B for match and append or recertification, but the D&B connector could not process them successfully. The following process has been created in SnapLogic to automatically pick the records that the D&B connector could not process and resubmit them for reprocessing.
  1. Create a batch of organizations' records that has to be sent to D&B for match and append or recertification process.
  2. Run the D&B connector by using the SnapLogic pipeline to process or enrich organizations' records with the D&B data.
    If for some reasons the D&B connector is unable to process some of these records, then the failed records are stored for reprocessing into the "failed records" file, which is stored in AmazonS3 (Storage3).
    • The organization records that the D&B connector could not process successfully during D&B match and append, are written in the GLB-xyz.connector_errors.log file and stored in AmazonS3.
    • The organization records that the D&B connector could not process successfully during D&B recertification, are written in the REF-xyz.connector_errors.log file and stored in AmazonS3.
    XYZ refers to the name of file generated based on the current date and time. The format is YYYYMMDDHH24MMSS.
    Note: SnapLogic is deprecated since March 14, 2020. To continue using SnapLogic, you must have a separate license from SnapLogic.
  3. After the D&B connector completes processing all the records, the SnapLogic pipeline automatically picks up the "failed records" file that is stored in AmazonS3, and tries to rerun the connector to reprocess these records for the first time.
  4. If the D&B connector fails to reprocess these records, then the failed records are again stored into the "failed records" file to reprocess them for the second time.
    Note: The D&B connector retries to reprocess the organizations' records second time only if the error code for such records is 13 that is INTERNAL_ERROR.
  5. If the D&B connector fails to reprocess these records in the second run, then it just stores these records into the "failed records" file, but does not try to reprocess it third time.
  6. After two failures, you need to manually check the failed records that are stored in AmazonS3, figure out the reason that is causing the failure, fix the problem, and then rerun the connector to reprocess these failed records.
    Note: There is no automated mechanism to notify that the D&B connector failed to reprocess the organizations' records. The connector catches exceptions and returns an appropriate error code with its description for all the records that the connector failed to reprocess. These details are stored in a file on AmazonS3.