Hey everyone, We’re currently seeing an issue where Airbyte pipelines aren’t starting properly, and no new logs are appearing after restart attempts. Several connections have been stuck in a running state for over two hours with no progress, and stopping/restarting them doesn’t help. It seems to affect multiple connections. We’ve already opened a support ticket with Airbyte, is anyone else here experiencing the same issue?

Yes, several users have reported similar issues where Airbyte syncs or pipelines get stuck in a "running" or "pending" state, and restarting jobs or even the entire Airbyte instance does not resolve the problem. Here are some relevant findings from the knowledge sources: - Stuck Syncs and No New Logs: Users have experienced syncs that remain in a running state for hours with no progress, and logs stop updating. Restarting jobs or pods sometimes temporarily resolves the issue, but it can recur. In some cases, only cancelling the stuck jobs individually or restarting all Airbyte pods helped, but this is not a permanent fix. For example, one user noted that after restarting pods, the issue was temporarily resolved, but jobs would hang again after a few days. They resorted to a daily restart of all pods as a workaround, though this is not ideal as it kills running jobs [Syncs getting stuck](https://discuss.airbyte.io/t/1916) [Temporal Scheduler Causing Multiple Syncs to Hang](https://discuss.airbyte.io/t/1293). - No New Jobs Launched: There are reports of Airbyte services getting stuck where no new job pods are launched, often accompanied by errors in Temporal and issues with workload claiming. This can be exacerbated by resource constraints, thread leaks, or Temporal rate limiting [airbyte services stuck where no new job pods are launched](https://github.com/airbytehq/airbyte/issues/68115). - MinIO Storage Issues: In Kubernetes deployments, a common root cause is the MinIO persistent volume filling up (default is 500MB), which prevents new jobs from starting and can cause syncs to hang indefinitely. Deleting old logs from MinIO or increasing the storage allocation has resolved the issue for several users. You can do this by deleting logs in

/storage/airbyte-storage/job-logging/workspace

and/or increasing the MinIO PVC size in your

values.yaml

 [All sync jobs hanging indefinitely](https://github.com/airbytehq/airbyte/issues/55812). - Resource Constraints: Insufficient memory or CPU allocation can also cause workers to hang or not start. Increasing resource limits and requests for Airbyte components (especially workers and Temporal) has helped in some cases [Sync Stuck in Running / K8s](https://discuss.airbyte.io/t/680). - Version-Specific Bugs: Some issues are related to specific Airbyte versions or missing configuration after upgrades. Ensuring your deployment files (like

docker-compose

or Helm values) are up to date with the required environment variables and settings for your Airbyte version is important [0.40.7 Worker Micronaut Update Causing Worker to Constantly Crash](https://discuss.airbyte.io/t/2648). What you can try: - Check MinIO storage usage and clear old logs or increase the PVC size if needed. - Ensure your Airbyte deployment has sufficient CPU and memory. - Restart all Airbyte pods or containers (sometimes a full restart is needed to clear stuck jobs). - Make sure your deployment configuration matches the requirements for your Airbyte version. - If the issue persists, monitor the logs for errors related to Temporal, MinIO, or resource exhaustion. If you’re seeing this issue, you’re not alone—others in the community have encountered it as well. The most common root causes are storage exhaustion (especially MinIO), resource constraints, or version/configuration mismatches. If you’ve already opened a support ticket, providing details about your storage, resource allocation, and recent logs will help the support team diagnose the issue more quickly.

whats your version ?

Version of?

im on airbyte cloud, same thing

It’s happened on any type of connection, for example connection Postgres -> Redshift. The logs show repeated “Workload not claimed”

yeah all kinds of connections, even with custom connectors

Me too

Same happening here

seems like problem is solved on our side ?

I see now it is work but it takes more time to run more than usual. Hope it will totally fix soon

Hi everyone, thank you for flagging this. I had informed the team when I saw these messages. Let me know if you're still having any issues

everythings back to normal for us, thx 🙏

Everything is back to normal for us also, thanks! 🙂