FME - Some customers are experiencing delays in scheduled exports of impressions

Incident Report for Harness

Postmortem

Incident Summary

Harness FME (Feature Management & Experimentation) faced substantial delays in scheduled impressions data exports on Jul 2, 2026. This issue stemmed from performance degradation within Tinybird's infrastructure, affecting query execution crucial to our export pipeline.

Root Cause

The core issue was a temporary performance degradation on the provider's infrastructure. This directly impacted the metadata retrieval endpoint, which failed to return job IDs intermittently. Consequently, completed export jobs underwent repeated retries, leading to a backlog in the export queue.

Impact

  • The export backlog accumulated, peaking at more than 6 hours behind the planned schedule.
  • No data loss was detected during the incident.

‌

Mitigation

  1. Adjusted Temporal workflows: Extended timeouts from ~30 to ~50 minutes and increased polling attempts from ~180 to ~300.
  2. Expanded resource capacity.
  3. Traffic redirection: Systematically shifted export workloads over to an optimized in-house cluster.
  4. Manual intervention: Terminated stalling workflows stuck in retry loops from failed metadata lookups.

‌

Next Steps

Complete the migration of all remaining export jobs to the internal analytics cluster (In progress).

Posted Jul 09, 2026 - 12:34 PDT

Resolved

This incident has been resolved.
Posted Jul 03, 2026 - 09:11 PDT

Update

We are continuing to monitor results while the backlog is worked through.
Posted Jul 02, 2026 - 16:31 PDT

Update

We are seeing the backlogged items worked through and continuing to monitor results.
Posted Jul 02, 2026 - 13:10 PDT

Monitoring

A fix has been implemented and we are monitoring the results.
Posted Jul 02, 2026 - 08:48 PDT
This incident affected: Prod 3 (FME), Prod 1 (FME), and Prod 2 (FME).