Outbound Campaign API 409 Conflict on Campaign Name Uniqueness

Is it possible to bypass the strict uniqueness check for outbound campaign names when deploying via Terraform? The provider returns a 409 Conflict even when targeting different orgs or environments. The payload includes a unique ID, but the API seems to validate against a global scope.

{
 "name": "Outbound_Campaign_A",
 "description": "Test campaign",
 "type": "PREDICTIVE"
}