PureCloudPlatformClientV2 handles the custom object relationship traversal endpoint differently than raw REST, so I constructed a Java payload with sourceRecordId references and a depthLimit directive set to 5 before hitting /api/v2/analytics/custom-object-relationships/traverse. PureCloudPlatformClientV2 throws a 422 Unprocessable Entity right after the second atomic GET call, and it’s pretty clear the relationship type matrix or circular reference checking logic is failing the permission scope verification pipeline. I’ve already wired up explicit pagination triggers and callback handlers for the external viz tool, but the stack overflow warning still triggers when tracking node retrieval rates and generating traversal audit logs, so I need the exact JSON schema for the traversal validation logic that exposes a relationship traverser for automated object management without hitting the maximum recursion depth limit.
Are you actually using the Java SDK or just routing through axios for the traversal call? PureCloudPlatformClientV2 doesn’t expose a native method for that endpoint so you’ll need to drop to raw HTTP and swap depthLimit for maxDepth in the body since the Java client auto-injects it as a query param instead of JSON.
{
"sourceRecordId": "a1b2c3-d4e5-f6g7-h8i9-j0k1l2m3n4o5",
"relationshipType": "custom_object_relationship_v1",
"maxDepth": 3
}
Circular references usually trip the guard past two hops anyway.