DAT Solutions Internal

Back
Oct 1, 2025 4:22 PM PDT

Billing for Extended Network Load Postings has not billed since October 31, 2024

Updates

  • Nov 7, 2025 9:55 AM PST

    The harvester job that collects billing data from the asset_post_txns table of the origami schema of the bapprod database for Extended Network Load postings has not run successfully since October 31, 204. The estimated revenue impact is approximately $10k. The current working theory is that the table associated with this data has grown so large that the harvester job is timing out and thus data is not being sent to Salesforce for billing.

    Resolved
  • Oct 26, 2025 10:12 AM PDT (1 week, 5 days, and 42 minutes earlier)

    The harvester job that collects billing data from the asset_post_txns table of the origami schema of the bapprod database for Extended Network Load postings has not run successfully since October 31, 204. The estimated revenue impact is approximately $10k. The current working theory is that the table associated with this data has grown so large that the harvester job is timing out and thus data is not being sent to Salesforce for billing. The incident was mitigated by turning off the harvester job that was failing and implementing changes to ensure data would be recorded again, such as truncating the asset_post_txns table and adding a primary key. Additionally, the table maintenance (truncate + primary key) is completed (per CSB-2450 being Resolved) and the harvester/writes have been stable since Oct 10 without timeouts - it’s reasonable to mark INC-1124 as mitigated while leaving long‑term improvements (migrating off CSB to Snowflake) to separate workstreams.

    Monitoring
  • Oct 1, 2025 4:22 PM PDT (3 weeks, 3 days, 17 hours, and 50 minutes earlier)

    The harvester job that collects billing data from the asset_post_txns table of the origami schema of the bapprod database for Extended Network Load postings has not run successfully since October 31, 204. The estimated revenue impact is approximately $10k. The current working theory is that the table associated with this data has grown so large that the harvester job is timing out and thus data is not being sent to Salesforce for billing.

    Investigating