Hello :wave::skin-tone-4: In the past 2 weeks, we...
# ory-network
r
Hello 👋🏽 In the past 2 weeks, we've gotten 2 occurrences of
504 Gateway Timeout
errors when calling Ory Keto API endpoints. Is there something we can do to investigate what's causing these? We have the Cloudflare Ray IDs if useful (latest occurrence was this morning)
m
Hello @refined-architect-59368 Yes, the Cloudflare Ray IDs are very useful for investigation, please share them along with: • Timestamps of when the errors occurred • Project ID / slug • Exact endpoints that timed out (e.g.,
/relation-tuples/check
,
/relation-tuples/batch/check
, etc.) • Full response details if available (status code, raw body, response headers including
X-Request-Id
and
cf-ray
)
Often a 504 error is caused by a failing webhook target, but I assume that is not the case here.
You can also check these 2 things: 1. Request volume: Check if your request rate was unusually high around the time of the errors. If traffic from a single IP exceeded plan rate limits, you may have been rate-limited rather than experiencing a true timeout. [rate limits docs] 2. Concurrent/inflight requests: Ory has inflight rate limits on certain endpoints. For
/relation-tuples
paths, check if there were concurrent requests from the same source that could have triggered this. [endpoint rate limits]