Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How can adtechs recover from aggregations failures? #325

Open
palenica opened this issue Feb 16, 2022 · 1 comment
Open

How can adtechs recover from aggregations failures? #325

palenica opened this issue Feb 16, 2022 · 1 comment

Comments

@palenica
Copy link
Collaborator

How can adtechs recover from failures (such as a misconfigured batch)?

@ruclohani
Copy link
Collaborator

Aggregation service jobs can fail in certain scenarios e.g. job misconfiguration, coordinator service outages, etc.
Adtech should use the output of getJob API to look at the return code, message and error summary.

If the job is misconfigured, the aggregation service will provide details on error resolution in the return message. If the job succeeds partially, with some invalid reports, the response error summary will have more details about the report error counts with corresponding description. A failed job can be rescheduled using the createJob API after resolving issues (if any) or in case of any transient issues.

In certain rare cases, a failed job may result in aggregatable report accounting budget consumption without getting summary results. We are exploring solutions to help recover accidently consumed aggregatable report accounting budget in such scenarios. In the meantime, we advise ad techs to generate and keep debug reports, since processing them aren’t limited by aggregatable report accounting budget (see https://github.com/privacysandbox/aggregation-service/blob/main/docs/debugging.md).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants