@kapa.ai Why would i be getting '503 Service Temporarily Unavailalbe' error?

503 Service Temporarily Unavailable in Airbyte The 503 error can occur in a few different contexts within Airbyte. Here are the most relevant causes based on the knowledge sources: 1. Facebook Marketing Connector A 503 response from the Facebook API typically means the Facebook API service is temporarily unavailable. The connector handles this as a transient error and will automatically retry. [Facebook error handling] If retries are exhausted, you'll see a message like: > "The Facebook API service is temporarily unavailable. This issue should resolve itself, and does not require further action." This can also be triggered by request timeouts — for example, when fetching large amounts of ad-level insights data with breakdowns, Facebook may return a 503 with a message like "Your request timed out. Please try a smaller date range, fetch less data, or use async jobs." [Facebook timeout issue] 2. Google Sheets Connector A 503 from the Google Sheets API is treated as a temporary issue on Google's side. The error message will be: [Google Sheets error handling] > "There was an issue with the Google Sheets API. This is usually a temporary issue from Google's side. Please try again." 3. Recharge Connector 503 errors (e.g., "A 3rd party service on which the request depends has timed out") are handled by Airbyte's

DefaultErrorHandler

with exponential backoff, retrying up to 10 times. [Recharge performance] 4. Airbyte Platform / abctl Installation If you're seeing 503 errors in the Airbyte UI or API after installing with

abctl

, it may be due to a misconfigured ingress pointing to a non-existent service (

webapp-svc

instead of

server-svc

). The workaround is to manually edit the ingress to point to

airbyte-abctl-airbyte-server-svc

. [abctl ingress issue] General Recommendation In most cases, 503 errors are transient and Airbyte connectors will retry automatically. If the error persists: • Check if the upstream API is experiencing an outage. • Try reducing the amount of data requested (smaller date ranges, fewer fields). • For platform-level 503s, verify your Airbyte deployment's ingress configuration. Could you share which connector or context you're seeing this error in? That would help narrow down the cause further. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.