DAT Solutions Internal
DICE error prevents certificates from ocr to carrierwatch
Updates
-
Feb 23, 2026 11:04 AM PST
We are receiving an error when working Dice. Dice has an impact on CarrierWatch. If Dice is not working we cannot get insurance certificates to go through to OCR to be able to then publish into CarrierWatch. Resolution was achieved by temporarily rolling OCR back to the Hillsboro server to re-establish ABBYY licensing and clear the backlog, then restarting DICE to process certificates. After the licensing and connectivity issues were resolved, OCR was migrated back to AWS and DICE was brought online with end-to-end validation showing the DICE → OCR → CarrierWatch pipeline functioning again.
Resolved -
Feb 20, 2026 10:04 AM PST (3 days, 1 hour, and 1 second earlier)
We are receiving an error when working Dice. Dice has an impact on CarrierWatch. If Dice is not working we cannot get insurance certificates to go through to OCR to be able to then publish into CarrierWatch. Mitigation actions included increasing CPU resources on bvtdice03 to handle spikes, stopping the DICE instances to migrate OCR, and rolling OCR back to the Hillsboro server during the OCR migration to restore licensing and reduce timeouts. After the migration, DICE was brought back online and the team revalidated the end-to-end workflow (DICE → OCR → CarrierWatch).
Monitoring -
Feb 18, 2026 6:21 AM PST (2 days, 3 hours, and 43 minutes earlier)
We are receiving an error when working Dice. I believe this may be related to the AWS switchover. Dice has an impact on CarrierWatch. If Dice is not working we cannot get insurance certificates to go through to OCR to be able to then publish into CarrierWatch.
Investigating