I am retrieving the All Subscribers list via SOAP calls then using the Customer Key returned to then create a Triggered Send definition.
For one particular customer, the All Subscribers list Object that is returned does not seem to exist. A List object is returned by Marketing Cloud, however the CustomerKey of this List object does not match the CustomerKey of All Subscribers list that is within Marketing Cloud. This is not something I have run into previously.
When I attempt to then use the CustomerKey of this List to create a TriggeredSend, I receive the general, unhelpful error from SOAP (Error Code: 2 with the generic message containing a log id), and from Rest I receive the error 'MCMS_UTM_Validation_InvalidValue_list: Unable to find List All Subscribers - xxxxxx'. (xxxxxx rather than the number as I do not know if this is sensitive data or not)
When I retrieve an existing Triggered Send definition via Rest Api, all have the correct All Subscriber CustomerKey defined.
I have tried querying for All Subscribers a few ways using SOAP retrieve of a List:
ListName EQUALS 'All Subscribers' ListName LIKE 'All Subscribers' CustomerKey LIKE 'All Subscribers'
All return only a single List definition, all the incorrect definition. I cannot retrieve the actual All Subscriber List that exists within Marketing Cloud via SOAP no matter how much I try.
CustomerKey EQUALS 'All Subscribers - xxxxxx' return no results.
I can get around this by hard-coding the CustomerKey for TriggeredSend definition creation, but I am unsure of what other repercussions this behavior may have in this BU (things like adding subscribers).
So, my question is: Has anyone run into this or have any suggestions for further filtering on Api calls to retrieve the correct List?
As additional information, this is within parent child business units. The Installed Package allowing Api access is created in the Parent and Licensed to the child. Within Marketing Cloud, the Parent and the Child both show the same CustomerKey for All Subscribers which is not that returning via Api. Auth tokens have been generated using both the Parent and the Child MIDS, both returning this same, seemingly-nonexistent All Subscriber list rather than the list shown with Marketing Cloud.