Data Connect – Delayed Table Refreshes

Update timeline

1. investigating Oct 19, 2026, 01:03 PM UTC

   We are aware of reports from some clients that certain Data Connect tables are not refreshing as expected. The following tables are currently affected: - da_funding - da_application_individual_account - da_applicants_custom_questions This delay will not cause your daily processes to fail. However, any downstream reports that use these tables may not show the most recent data until the issue is resolved. Our team is investigating the issue and will share an update with next steps as soon as more information is available. We apologize for any inconvenience and appreciate your patience.

2. investigating Oct 19, 2026, 04:09 PM UTC

   Our team is still investigating the refresh delay affecting Data Connect tables Downstream reports that use these tables may still show older data until the issue is resolved. We’ll post another update as soon as we have more information. Thank you for your patience.

3. monitoring Oct 19, 2026, 08:51 PM UTC

   While investigating, our team found additional Data Connect tables that were not refreshing as expected. The affected tables have now been fixed and will be refreshing normally going forward. What you may notice: For the affected tables, you may notice around 9 extractions, with missing data stored in the 2026-10-19 mid day extraction. da_funding: The missing data for da_funding will be filled in during tomorrow’s scheduled refresh. Your daily processes will keep running normally. We’re monitoring the tables to make sure refreshes continue as expected, and we’ll post another update after tomorrow’s refresh finishes. Thank you for your patience.

4. monitoring Oct 20, 2026, 04:23 PM UTC

   We’re still monitoring a refresh issue that could affect a number of Data Connect tables. Our team has identified the following 37 tables that were not refreshing as expected: da_applicants_custom_questions da_applicants_truncated da_application_account_last_modified da_application_individual_account da_application_individual_account_custom_questions da_bl_specific_loan_info da_ml_property_info da_pl_specific_loan_info da_vl_specific_dealership_processing da_vl_specific_loan_info da_vl_specific_vehicle da_company_current_address da_company_mailing_address da_current_address da_current_employment da_declarations da_mailing_address da_monthly_debt da_monthly_income da_other_income da_previous_employment da_funding da_insurance_options da_custom_questions da_price_adjustments da_transaction_entity da_transaction_user_int da_underwriting_info da_spouse_current_address da_spouse_current_employment da_spouse_custom_questions da_spouse_declarations da_spouse_mailing_address da_spouse_monthly_debt da_spouse_monthly_income da_spouse_other_income da_spouse_previous_employment Clients on the earlier extraction time who reported missing data from the list of tables above should now see refreshed data. This delay was caused by a pipeline failure that our team fixed this morning, after the scheduled delivery time. This group will have data available at the expected time going forward (12 AM PST/ 3 AM EST). All other clients would have received data in this mornings refresh for the tables above. The following 5 tables are still not refreshed and are expected to be fixed by tomorrow’s refresh: da_audit_summary da_disbursements_check da_disbursements_deposit da_disbursements_fee da_disbursements_loan We apologize for the inconvenience and will post another update once the remaining tables are refreshed. If you run into any other issues, please submit a support ticket through our support portal.

5. identified Oct 21, 2026, 04:56 PM UTC

   We’re continuing to work on the refresh issue affecting a number of Data Connect tables. Since our last update, we have fixed the remaining 5 tables and found the cause of the delay in the other 37. Those tables are still one day behind, and we’re working to bring them current. We’ve also found a separate issue affecting clients with DEMO/BETA pipelines. These tables are now refreshing as expected and available on your pipeline to pull: da_audit_summary da_disbursements_check da_disbursements_deposit da_disbursements_fee da_disbursements_loan To prevent any gaps, this morning’s refresh included data from 10/14 through 10/20 (partial day) for these tables. You do not need to change your current data extraction process. The 37 tables below are still one day behind. Root cause: Our team found that a table used to capture data changes was not being refreshed at the correct frequency. The fix for this is in progress. We are now working to deliver the remaining missing day of data to your pipeline. da_applicants_custom_questions da_applicants_truncated da_application_account_last_modified da_application_individual_account da_application_individual_account_custom_questions da_bl_specific_loan_info da_ml_property_info da_pl_specific_loan_info da_vl_specific_dealership_processing da_vl_specific_loan_info da_vl_specific_vehicle da_company_current_address da_company_mailing_address da_current_address da_current_employment da_declarations da_mailing_address da_monthly_debt da_monthly_income da_other_income da_previous_employment da_funding da_insurance_options da_custom_questions da_price_adjustments da_transaction_entity da_transaction_user_int da_underwriting_info da_spouse_current_address da_spouse_current_employment da_spouse_custom_questions da_spouse_declarations da_spouse_mailing_address da_spouse_monthly_debt da_spouse_monthly_income da_spouse_other_income da_spouse_previous_employment DEMO/BETA pipelines: Clients with access to DEMO/BETA pipelines are also not seeing refreshed data in the 37 tables above. This is a separate issue. We have identified the cause and are working on a fix. Once it’s in place, we will deliver data for these tables from 10/14 to the present clients do not have a gap. We will share updates and ETA as soon as possible. We apologize for the inconvenience. If you run into any other issues, please submit a support ticket through our support portal.

6. monitoring Oct 22, 2026, 12:46 AM UTC

   Our team has fixed the issues behind this incident. This includes the refresh delay affecting the 37 Data Connect tables and the separate issue affecting clients with DEMO pipelines. All affected tables should now be refreshing as expected. What you may notice: You may see multiple extractions for 10/21. These come from backend testing we ran while validating the pipeline fix. If you use our Python scripts, no action is needed. The scripts will import all of the extractions correctly. If you use a custom process, please make sure it pulls every 10/21 extraction so that no data is missed. We’ll keep monitoring the refreshes and plan to close this incident tomorrow morning. Thank you for your patience. If you run into any issues, please submit a support ticket through our support portal.

7. identified Oct 22, 2026, 03:40 PM UTC

   We’ve found duplicate records in yesterday’s (10/21-10/22) refresh of the 37 Data Connect tables listed in our previous updates. Our team is investigating the cause and working on a fix. Because of this, we are no longer planning to close this incident this morning. We’ll post another update with a resolution and any steps you may need to take as soon as we have them. We apologize for the inconvenience and appreciate your patience. If you run into any other issues, please submit a support ticket through our support portal.

8. monitoring Oct 22, 2026, 08:30 PM UTC

   We’ve fixed the duplicate records in last night’s refresh of the 37 affected Data Connect tables. We’ve also fixed a separate delay that affected clients on the earlier extraction time. Details on each are below. Duplicate records in the 37 tables: We removed the duplicate records from the affected partition in last night’s refresh. We also fixed the backend code that caused the duplication, so it won’t happen again. If you use our Python scripts, no action is needed. Tomorrow’s refresh will remove the duplicate records from the affected partition automatically. If you use a custom process, please pull the latest extraction again to get the corrected version without duplicates. Missing data for clients on the earlier extraction time (12 AM PST / 3 AM EST): Some of these clients reported missing data this morning. This was caused by an internal pipeline failure, which we fixed at around 9 AM EST. The missing data is now available on the pipeline. If you use our Python scripts, no action is needed. The data will flow through your pipeline automatically. If you use a custom process and did not pull the missing extraction this morning, please pull it now or in the next 7 days. We’ll keep monitoring the refreshes and post another update once we confirm everything is running as expected. We apologize for the inconvenience and appreciate your patience. If you run into any other issues, please submit a support ticket through our support portal.