Looking for advice on a data gap in our legal discovery workflow.
The bulk export job via POST /api/v2/quality/assessments/exports returns the final scores but strips the interaction_summary and agent_id fields. This breaks the chain of custody for compliance audits. The job completes with status completed, yet the CSV lacks essential metadata. Is this a known limitation of the WFM Quality API or a configuration issue?
Make sure you include the interaction_summary and agent_id in the fields array of your export request body. The API defaults to minimal output if specific columns are not explicitly requested.
This issue stems from the default field set in the Quality export payload. While adding fields works, do not overlook the interaction_id if you need to cross-reference with telephony metrics. I usually append conversation_uuid too, since the agent_id can sometimes map to a team rather than an individual in blended queues.
If I recall correctly, the API schema validation is strict. Missing explicit field definitions triggers a silent failure in column mapping.
Error: Invalid field configuration. Expected array of strings.
Use Terraform to enforce the fields block in the export job resource. This prevents manual API errors.
If I remember right, the suggestion above hits the nail on the head. coming from zendesk where exports were static, explicitly defining those fields in the gc request body is the only way to preserve that metadata.