running the java against /api/v2/routing/interactionattributes and the batch update wrapper keeps failing on etag validation. generator pulled the latest spec, but model classes are stripping the optimistic lock headers when we map dynamic attribute schemas to the request body. i’ve got an async job syncing external data, throws a 409 Conflict whenever two workers hit the same interaction definition. payload construction looks fine locally, client just drops the if-match header mid-flight. here’s what the generated client does with the etag:
var request = new PatchInteractionAttributesRequest();
request.setAttributes(dynamicMap);
request.setIfMatch(currentEtag);
var response = routingApi.patchInteractionAttributes(interactionId, request);
if-match never actually reaches the gateway. seems like the openapi-generator template overrides header injection for routing patch ops. just checked wire logs, doesn’t inject it properly, flattens custom headers into the query string instead.