Ingest issues for some customers

Final update

We can confirm that the fix was applied uniformly to all impacted and potentially impacted environments; no teams should see ingest errors related to this issue anymore.

1. Resolved · Apr 10, 17:24 UTC
   We can confirm that the fix was applied uniformly to all impacted and potentially impacted environments; no teams should see ingest errors related to this issue anymore.
2. Monitoring · Apr 10, 15:21 UTC
   We are continuing to work on the systemic solution and monitor. We'll leave the incident open until we're able to confirm the issue won't recur.
3. Monitoring · Apr 10, 14:32 UTC
   The manual fix has been applied to all environments.
4. Monitoring · Apr 10, 14:19 UTC
   We've applied the manual fix to nearly all affected datasets (less than 1% remaining). The systemic solution is still in progress.
5. Identified · Apr 10, 13:55 UTC
   We've identified a manual fix and are deploying that by hand to each affected environment, while also investigating a systemic solution.
6. Identified · Apr 10, 13:46 UTC
   We have further narrowed down that only teams on Classic environments are currently seeing issues. We are figuring out mitigation mechanisms at the moment.
7. Identified · Apr 10, 13:41 UTC
   We have confirmed reports of some teams getting issues ingesting their data. We have identified a probable source behind this behavior and are currently trying to correct it.