Looking for advice on the payload structure required for the api/v2/users/{userId}/remove endpoint when triggered from a GDPR compliance flow in Genesys Cloud Release 2024-12 (v13.2, AWS London). The ServiceNow Data Action returns a 400 Bad Request with the following error:
“The request body is missing the required ‘consent_record_id’ field in the nested compliance object.”
Despite the documentation stating that this field is optional for automated purges, the webhook execution fails consistently. Can anyone confirm if this is a known regression in the latest GC release or if the ServiceNow REST API expects a specific JSON schema version?