- TLC Home Home
- Discussions Discussions
- Documentation Documentation
- Knowledge Base Knowledge Base
- Education Education
- Blog Blog
- Support Desk Support Desk
06-12-2023 07:23 AM
In AudienceStream|Connector|Google Ads Customer Match (Tealium-Provided Credentials)
In some action created in Google Ads Customer Match (Tealium-Provided Credentials) connector, I have encountered an API Error 400.
It says: "Action Failure: API Error - 400: Error while running Offline User Data Job. Multiple requests were attempting to modify the same resource at once. Retry the request."
what is causing this error?
Thanks in Advance!
06-12-2023 08:27 AM
The error you're seeing, "Multiple requests were attempting to modify the same resource at once. Retry the request", is indicating a concurrency issue.
Google Ads API is designed to allow one operation at a time on a specific resource. If two or more requests are trying to modify the same resource simultaneously, it leads to a conflict, and the Google Ads API will throw an error message, which is what you're seeing.
This could potentially occur if you have multiple actions in your Google Ads Customer Match connector that are attempting to update the same audience list at the same time. Or, if you have other processes outside of Tealium (like scripts or other applications) that are also trying to modify the same Google Ads resource at the same time as Tealium.
Here are few suggestions on how to address the issue:
Ensure unique resources for each action: Try to isolate which resource (for example, a specific audience list) is causing the issue and see if it's being modified by more than one action or process. If possible, create unique resources for each action to avoid any conflict.
Synchronize the actions: If multiple actions must modify the same resource, try to synchronize them so they don't occur at the same time. You might be able to do this by scheduling the actions at different times or by adjusting their triggering events so they don't overlap.
Retry logic: Implement a retry logic in case of failures. This is not a direct solution to the problem but might help in scenarios where the error is not consistent and happens sporadically.
Copyright All Rights Reserved © 2008-2023