DAT Solutions Internal

Updates

• Sep 14, 2026 12:49 PM PDT

  During TT Salesforce migration (Sept 11-12), 62 active customer broker accounts
  lost MC/DOT data. These fields are required for load postings to appear to carriers.

  • Spike: 68 affected accounts (23x normal; 62 active, 6 test)
  • Root Cause: TT data migration — MC/DOT field mapping failed
  • Customer Impact: Brokers cannot post loads; carriers won't see postings
  • Complaints: 1 confirmed; more expected
  • Workaround: None (MC is required)

  Last modified by: LeanData Integration (09/11), TT Data Migration (09/11),
  Integration Admin (09/12)

  Resolved
• Sep 14, 2026 6:25 AM PDT (6 hours and 23 minutes earlier)

  During TT Salesforce migration (Sept 11-12), 62 active customer broker accounts
  lost MC/DOT data. These fields are required for load postings to appear to carriers.

  • Spike: 68 affected accounts (23x normal; 62 active, 6 test)
  • Root Cause: TT data migration — MC/DOT field mapping failed
  • Customer Impact: Brokers cannot post loads; carriers won't see postings
  • Complaints: 1 confirmed; more expected
  • Workaround: None (MC is required)

  Last modified by: LeanData Integration (09/11), TT Data Migration (09/11),
  Integration Admin (09/12) Resolution: MC/DOT numbers restored for all affected accounts.

  What We Did:
  - Retrieved original MC/DOT values from OwnBackup (Salesforce backup) + Snowflake as backup source
  - Phase 1: Restored 62 active customer accounts (Sept 13, 2:20 PM)
  - Phase 2: Identified and restored ~2,000 additional accounts with NULL MC/DOT (Sept 13, 5:11 PM)
  - Validation: DeeDee's daily report confirmed all accounts normalized (Sept 14, 6:32 AM)

  Verification:
  - Daily report spike (68 accounts) → normalized to baseline (3-5 accounts)
  - No customer complaints since restoration
  - Load postings now display MC/DOT correctly to carriers

  Status: RESOLVED — incident ready for closure

  Monitoring