Quick question about the data integrity of outbound dialing interactions when exported for legal discovery purposes. We are noticing that specific compliance metadata, specifically the ‘consent_timestamp’ and ‘regulatory_category’ fields, are null in the final JSON payload, even though the Architect flow explicitly sets these attributes before the dialing action.
The environment is Genesys Cloud v2024.08, London region. The outbound campaigns are configured with strict DNC and compliance rules. When we trigger a bulk export job via the /api/v2/analytics/conversations/details/query endpoint, filtering for direction=outbound, the resulting records lack the custom attributes defined in the Architect flow.
Here is the relevant snippet from the Architect flow configuration:
attributes:
consent_timestamp: "${interaction.timestamp}"
regulatory_category: "GDPR_EU"
legal_hold_tag: "true"
The bulk export job completes successfully with a 200 OK status. However, the chain of custody documentation requires these specific fields to be present for audit trails. The standard digital channel exports (WhatsApp/Chat) preserve these attributes correctly. Is there a known limitation or configuration requirement for outbound voice campaigns to ensure custom attributes are persisted in the analytics export payload? We need to ensure the exported data meets legal standards without manual post-processing.