Hello, Thanks for the clarification. I didn't notice that screenshot when the case was escalated to me, and that helps to clarify the problem quite a lot.
I'm not sure how that shared set got into the state it is, since it appears to be from 2017 and our change history only goes back to January 2019 at the moment. However, what you can do is whenever you want to apply a new shared set to a campaign, you can fetch all enabled shared sets for that campaign and disable them, ensuring that only the new one is enabled. This shouldn't be too much overhead, as even if you're applying to multiple campaigns you can do the fetch and the disable in bulk for the existing shared sets. Does this workflow sound feasible? Regards, Mike, Google Ads API Team ref:_00D1U1174p._5001UaSxGg:ref -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog: https://googleadsdeveloper.blogspot.com/ =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API and Google Ads API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/adwords-api/8JHLW000000000000000000000000000000000000000000000QA88I400JRP3jatMSryuaw5uUaBYkQ%40sfdc.net.
