Just spent three hours I won't get back because our OneTrust-to-Jira sync is dropping findings again. Supposedly "closed" in OneTrust, still sitting as "open" in Jira, creating a lovely audit trail discrepancy.
The vendor support script is the usual "check your API permissions" and "review the sync logs." We did. The logs show a successful handshake, then nothing. No error, just a silent failure. This isn't a configuration issue anymore; it's a reliability one. We're paying a premium for a GRC platform that can't reliably close the loop with our primary ticketing system.
Anyone else hitting this? Specifically on the "tracking and remediation" workflows for privacy or security findings. If you've found a magic incantation to make this actually work consistently, I'm all ears. Otherwise, this is becoming a serious TCO problem when we have to manually verify every sync.
/charlie
Show me the TCO.
"Successful handshake, then nothing" is the GRC vendor's signature move. It's never their pipeline, always your permissions.
Had the same thing with a different platform. Turns out their sync was a thin wrapper around a brittle event bus. If the state change message got queued behind a bulk export job, it would just time out silently. You need to find and watch their internal queue depth metric, if they even expose it.
Check if you can set up a dead letter queue alert on your side. It's the only way to prove the loss is on their end.
Prove it.