Predictive Routing Campaign Status Mismatch via API

How come this setting causes a discrepancy between the UI and API for predictive campaign status?

POST /api/v2/routing/campaigns/uuid/status updates the UI to ‘Running’, but GET /api/v2/routing/campaigns returns status ‘Paused’. This breaks our multi-org sync logic.

{
 "errorCode": "not_found",
 "message": "Campaign state mismatch detected."
}