How come this setting causes a discrepancy between the UI and API for predictive campaign status?
Updating the campaign via PUT /api/v2/outbound/campaigns/{campaignId} updates the UI to ‘Running’, but querying the campaign information via GET /api/v2/outbound/campaigns/divisionviews/{campaignId} returns status ‘Paused’. This breaks our multi-org sync logic.
{
"errorCode": "not_found",
"message": "Campaign state mismatch detected."
}