What does mean for DECRYPTION_KEY_NOT_FOUND error?

[yingli19]

"result_info": {
"return_code": "SUCCESS_WITH_ERRORS",
"return_message": "Aggregation job successfully processed but some reports have errors.",
"error_summary": {
"error_counts": [{
"category": "DECRYPTION_KEY_NOT_FOUND",
"count": 13,
"description": "Could not find decryption key on private key endpoint."
}, {
"category": "NUM_REPORTS_WITH_ERRORS",
"count": 13,
"description": "Total number of reports that had an error. These reports were not considered in aggregation. See additional error messages for details on specific reasons."
}],
"error_messages": []
},
"finished_at": "2025-05-07T07:37:58.869281942Z"
},

[nlrussell]

Per our error codes and mitigations guide, this error happens when the key_id supplied in the report's payload was not found. Please try the mitigation steps in this guide and let us know if the issue persists.

[yingli19]

The Key_id should be generated by the Chrome browser when Aggregatable Reports send, right? Why does the case of key_id not found occur

[nlrussell]

Do you use Attribution Reporting API? If so, this error may be caused by an issue with the trigger registration which happens in the browser. Check that the trigger has been registered with the correct cloud using the aggregation_coordinator_origin field: instructions here.

This error can also be returned when there's a mismatch of decryption key and cloud provider, i.e., when aggregatable reports encrypted for one cloud are aggregated with an Aggregation service running on another cloud provider. Validate the public key endpoint used to encrypt the aggregatable reports. On your raw aggregatable report received in your .well-known reporting endpoint, you should be able to see the aggregation_coordinator_origin field. For GCP, the value should be https://publickeyservice.msmt.gcp.privacysandboxservices.com. For AWS, it's https://publickeyservice.msmt.aws.privacysandboxservices.com. If aggregation_coordinator_origin is not stated in the Attribution Reporting API / Private Aggregation API, the default will be AWS. For Attribution Reporting API, you can specify your cloud provider by passing it in the trigger registration. For Private Aggregation API, you will have to define the aggregationCoordinatorOrigin using the example in Aggregation coordinator choice section in the Private Aggregation API explainer. Please specify https://publickeyservice.msmt.gcp.privacysandboxservices.com as the aggregationCoordinatorOrigin.