Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

<@U04S8PLJWMT> I'm getting this recurring error in temporal, any ideas?
```{"level":"info","ts":"2026-03-19T01:06:48.800Z","msg":"history client encountered error","service":"matching","error":"Activity task already started.","service-error-type":"serviceerror.TaskAlreadyStarted","logging-call-at":"/home/runner/work/docker-builds/docker-builds/temporal/client/history/metric_client.go:103"}```

The error you're seeing — `"Activity task already started."` with `service-error-type: serviceerror.TaskAlreadyStarted` from Temporal's matching service — is a known issue reported by other Airbyte users running self-hosted deployments (including on EKS and Kubernetes environments). [<https://github.com/airbytehq/airbyte/issues/59730|Temporal context deadline exceeded on eks>; <https://github.com/airbytehq/airbyte/issues/68115|airbyte services stuck>]
This error appears in Temporal's history/matching service and is often associated with broader symptoms such as:
• Airbyte services becoming stuck
• No new job pods being launched
• `context deadline exceeded` errors alongside the `TaskAlreadyStarted` errors
Unfortunately, the knowledge sources available to me do not contain enough detail about the *root cause or a confirmed fix* for this specific error. The issues referenced are either still open or were closed without a detailed resolution being captured in the available content.
*Suggested next steps:*
1. Check the open GitHub issue [<https://github.com/airbytehq/airbyte/issues/68115|airbyte services stuck>] and the closed issue [<https://github.com/airbytehq/airbyte/issues/59730|Temporal context deadline exceeded on eks>] for any community updates or workarounds.
2. Consider restarting the Temporal service and the Airbyte worker/server pods, as this type of stuck-state issue in Temporal can sometimes be resolved by a restart.
3. If you're running on Kubernetes, check for resource constraints (CPU/memory) on your Temporal pods, as resource pressure can contribute to these kinds of errors.
I'd recommend following up directly on those GitHub issues or reaching out to the Airbyte community on Slack for more targeted assistance. :thumbsup: 0 button :thumbsdown: 0 button :information_source: *Tip:* Mention *@kapa.ai* in the thread for follow-ups or *DM the app* for *1-to-1* help.