Having some config trouble here… the quality management module in our eu-west byoc instance is failing to sync scores from external evaluations to the agent performance dashboard. the integration uses the standard rest api endpoint /api/v2/analytics/quality/scores but returns a 409 conflict error when attempting to post new evaluation records. the payload includes the correct agent id, campaign id, and evaluation date fields as per the documentation. however, the error response indicates a duplicate key violation on the evaluation_id field despite each record having a unique uuid generated via v4 standard. this issue started appearing after the last platform update in late october. the environment is strictly eu-west byoc with native data sources for wfm and quality. we have verified that no duplicate records exist in the source system and that the evaluation_id values are indeed unique. the problem persists across multiple agents and campaigns, suggesting a systemic issue rather than a data entry error. the dashboard shows stale data from three weeks ago while the api rejects new updates. this discrepancy affects our ability to report accurate quality metrics to stakeholders. we have attempted to clear the cache and restart the integration service but the issue remains. the error logs show the following message: ‘duplicate key value violates unique constraint “quality_score_pkey”’. this suggests that the platform is either not recognizing the unique identifier or is generating a collision internally. we need to understand if this is a known issue with the current version or if there is a configuration setting that needs adjustment. the impact is significant as it halts our weekly quality reporting process. any insights into resolving this conflict would be appreciated. we are unable to proceed with the monthly audit until this synchronization issue is resolved. the team has checked the network connectivity and firewall rules, confirming that the api calls are reaching the endpoint correctly. the issue is isolated to the score submission step. previous submissions with identical payload structures worked without issue prior to the update. this indicates a regression or a change in the validation logic on the platform side. we require a workaround or a fix to restore normal operations. the current state is blocking our compliance requirements.