@kapa.ai my api api/v1/stream_statuses/latest_per_run_state is taking too long

The knowledge sources do not contain enough information to answer your query about the

api/v1/stream_statuses/latest_per_run_state

endpoint specifically taking too long. However, based on related issues in the knowledge sources, slow API responses in self-hosted Airbyte instances have been linked to a few general causes: • Resource constraints: High memory/CPU usage on the host machine can cause API timeouts and slow responses. Checking

docker stats

to monitor container resource usage is a recommended first step. [Long loading time] • Memory leaks in server/worker containers: There have been known issues with memory leaks in Airbyte's logging system causing slowness. Restarting the

airbyte-server

and

airbyte-worker

containers has been suggested as a workaround, along with upgrading to the latest version. [Long loading time] • Large number of connections/syncs: Running many connections (e.g., 30+ syncing hourly) can put significant load on the backend APIs. [Long loading time] Suggested steps: 1. Check your container resource usage (

docker stats

or equivalent for Kubernetes). 2. Restart the

airbyte-server

and

airbyte-worker

containers. 3. Ensure you are on the latest version of Airbyte. If the issue persists, I'd recommend opening a GitHub issue at https://github.com/airbytehq/airbyte/issues with your Airbyte version, deployment method, and relevant logs for more targeted support. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.