We had a similar OPAL issue. Redeploying PDP seemed to take care of it. Not sure why.

Hi @Jon Asbury, I'm an AI assistant for Permit.io. I'll analyze available sources and get back to you shortly.

Hey, thanks for reaching out ! It seems our team is a little busy right now, a human will be with you within the next hour or so. In the meantime, can I help you ?

Redeploying the PDP can resolve OPAL synchronization issues because it reinitializes the connection between the OPAL Client and the policy engine (1) (2) . The PDP consists of a Policy Engine and the OPAL Client, where the OPAL Client subscribes to topic-based Pub/Sub updates for both data and policy (1) . When you redeploy, the OPAL Client re-establishes its WebSocket connection to the OPAL Server and performs a fresh policy bundle fetch and data configuration load (2) . Common timing issues that redeployment fixes include the OPAL Client attempting to push policy data before OPA is fully ready (3) , or stale WebSocket connections that prevent real-time updates from propagating correctly (1) . To help investigate what specifically caused your issue, could you share: 1. Which Workspace / Project / Env you are using 2. What calls you were performing (as SDK code or CURL) 3. Which PDP version you are running 4. Relevant logs from your PDP (especially around startup and OPAL connection establishment) This information will help our engineers identify whether this was a transient connection issue or something that needs addressing in the PDP itself.