Hi,
Yesterday, we started to see errors when we try to synchronise client shopping campaigns through our MCC account.
The error occurs when we try to remove the root node in the partition tree, before submitting an updated version of the tree. The specific error message is: EntityNotFoundReason.INVALID_ID. However, we have been following this process for a long time, and no recent changes have been made to our system.
In reviewing the IDs returned in the product partition report, it looks as though Google is identifying the root partition with a number that does not match the number that was returned from the API when the partition tree was created.
Can you confirm whether any changes have been made internally that would affect the synchronisation of partition trees? And how we can go about resolving this problem? At present all client accounts are failing to synchronise partition updates, including bid changes, so an early reply would be appreciated.
Regards,
John