looking for advice on handling 409 conflicts when pushing schedule changes via the WFM API. our AppFoundry integration is trying to sync external shift data for a mid-sized org. we are hitting version mismatch errors on the /api/v2/wfm/schedules endpoint. the response body indicates that the resource version on the server has changed since we fetched it. we are using the standard optimistic locking mechanism but the retries are failing because the window between fetch and update is too tight during peak load. is there a recommended pattern for handling these version conflicts at scale without causing a retry storm? we are seeing this happen consistently when updating more than 50 agents simultaneously. the error payload looks like this: {“errors”: [{“code”: “CONFLICT”, “message”: “Resource version mismatch”}]}. we are currently implementing an exponential backoff strategy but it feels inefficient. any insights on how other partners handle this synchronization issue would be appreciated. we are running the latest SDK version 3.5.2 and using multi-org oauth tokens for authentication. the issue persists across different tenants which suggests it might be a systemic limitation rather than a configuration error on our end.