Seeing 500 and errors on permit side of things. is...
# permit-saas
e
Seeing 500 and errors on permit side of things. is there currently an outage?
a
Hi @Engineering Swantide, I'm an AI assistant for Permit.io. I'll analyze available sources and get back to you shortly.
HTTP 500 errors don't necessarily indicate a Permit.io outage. When reviewing PDP logs, you may see HTTP 500 errors during sync operations, but these log entries do not indicate PDP disconnects or health check failures - they are typically related to client-side timeout configuration. (1) If you're seeing read timeouts during consistent update requests, the recommended configuration is to use the default
PDP_CONTROL_PLANE_TIMEOUT
(75 seconds) to allow the Permit API to manage request duration properly. Setting timeouts too low (for example, around 5 seconds) can cause unnecessary timeout errors in logs. To help investigate this issue, could you provide: 1. Which Workspace / Project / Env you are using 2. What calls you are performing (as SDK code or CURL) 3. Which PDP version you are running 4. Relevant logs from your PDP This will help determine if this is a configuration issue or something el
To learn more, see the sources I considered: [[1] Monitoring PDPs](https://docs.permit.io/how-to/monitoring-pdps)
z
Hi @Engineering Swantide we are investigating it, looks like some issue on the AWS side, with the DB. Will update soon.
j
also seeing elevated errors "could not fetch the api key scope in order to set the api context level"
z
It’s all one issue, related to the backend, will update asap.
e
gotcha, thank you for the update so far
o
Hey, the issue is resolved everything should go back to normal now. Let us know if you are still experiencing any issue
🙌 1
e
thank you, looking good so far over here
💜 1