Bot Configuration API 409 Conflict during Multi-Org Deploy

Can anyone clarify the expected behavior when pushing bot configuration via the platform API in a multi-tenant setup? We are receiving a 409 Conflict on the POST /v2/bots endpoint with message Resource conflict: Bot definition version mismatch. The client uses AppFoundry SDK v1.8. We are syncing across three orgs from a central pipeline. Is there a specific versioning header required to bypass this lock, or is this a known race condition in the current release?