No, just remove the feature and run your aggregation or request whatever was blocked before but looks like you figured that out!
Has anyone else who opened a case with support heard any updates on a possible cause for this issue?
Asking @cstepp @justinrhaines @Sushantmr
No updates on my case, I’m still waiting. I specifically asked them about the PREFER_UUID flag, they said Engineering has not provided any information about this.
Support has disabled a feature flag on our system and the issue seems to be fixed. I asked for details and this was the response, I don’t have access to the link so am requesting additional details.
Hello Carmen,
The Feature Flag name is: GOV_IDNARSENAL_USE_UUID_DURING_LINK_LOOKUP
Disabled around 8:15 AM, November 8, 2023.
I had a call with support this morning and they told me that turning off the feature flag you mentioned is different than removing the PREFER_UUID feature from the source config that I did.
Here are the additional details they sent me:
“GOV_IDNARSENAL_USE_UUID_DURING_LINK_LOOKUP”
This is an independent flag that when enabled the backend changes to use the uuid BEFORE the native_identifier when present.