A 504 Gateway Timeout with the WooCommerce connector can stem from a few different causes. Here's how to troubleshoot: 1. Rate Limiting / Too Many Concurrent Requests The WooCommerce connector applies a default rate budget of
5 requests per second and handles HTTP 429 responses automatically. However, if your hosting environment is more restrictive (shared hosting typically allows only 2ā5 req/s), the load from concurrent threads can indirectly cause timeouts. [
WooCommerce Limitations]
What to try:
ā¢
Reduce the
Number of Concurrent Threads in your connector configuration. The valid range is 2ā12, with a default of 4. Lowering this value reduces the load on your WooCommerce server. [
WooCommerce Source] 2. Ingress / Backend Timeout Configuration (Self-Hosted Airbyte) If you're running Airbyte on Kubernetes (Helm or abctl), your ingress controller may have timeout values that are too short. This is a known cause of 504 errors when creating or managing sources. [
Ingress Config]
What to try:
⢠Set appropriate
backend timeout values for the Airbyte server ingress. Short timeouts will cause 504 errors in the UI when creating new sources or destinations. [
Ingress Docs] 3. Low-Code Connector Builder (if applicable) If you built this connector using the low-code connector builder, there is a known issue where the connector works in the builder preview but returns a 504 when set up as a new source. This is typically related to the ingress/backend timeout issue mentioned above. [
Forum: 504 in Builder]
Summary of recommended steps:
1. Lower the
Number of Concurrent Threads (try setting it to 2).
2. If self-hosted, check and increase your ingress
backend timeout values.
3. Ensure your WooCommerce hosting environment can handle the request load.
If none of these resolve the issue, sharing your sync logs would help narrow down the root 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.