Design Bug – we are using transaction ID as ID for UAE events. This causes issues in Identity as multiple requests are coming in with same transaction ID, by design. Feeds rejects the second event with 409 (conflict). Identity needs this fix asap.
- We want to keep transaction id, because the traceability is good.
- We append a second ID generated at the time of the event which will be good for keeping feeds from rejecting the request.