Predictive Routing Campaign Update 422 on Contact List Assignment

{
“errors”: [
{
“message”: “Contact list id is invalid or does not exist in the specified organization.”
}
]
}

Encountering a 422 Unprocessable Entity when updating an outbound campaign via PATCH /api/v2/outbound/campaigns/{id}. The Premium AppFoundry integration validates the contact list ID against the tenant’s scope, yet the API rejects it. The OAuth client possesses outbound:campaign:write and outbound:contactlist:read. Is there a latency issue with contact list replication across multi-org environments?