How should I properly to handle schedule conflicts when pushing WFM data via the Platform API?
We are building a partner integration that syncs agent availability across multiple Genesys Cloud organizations.
The application uses multi-org OAuth to authenticate against each tenant.
When attempting to POST to /api/v2/wfm/schedules/agents, we receive a 409 Conflict error.
The response body indicates a ResourceConflictException.
The specific message states that the schedule overlaps with an existing entry managed by the native WFM module.
Our payload includes explicit start and end timestamps in UTC.
We have verified that the timezones are handled correctly in the conversion logic.
The issue seems to stem from the API rejecting updates to schedules that were created via the UI rather than the API.
Is there a specific header or flag required to override this protection?
We need to ensure our app can update these records without manual intervention in the console.
Any insights on the expected behavior for partner apps modifying native WFM data would be appreciated.