Receiving different results when requesting PermID's

Thank you for reaching out to us.

I can replicate this issue. The outputs are different for the same request.

I will contact the product team to investigate this issue.

Thank you for your response and for confirming that you can replicate the issue. Please could I ask that you include me in the response from your product team.

Thanks, John

The product team is working on this issue. I’ll keep you updated.

Hi @Jirapongse, Do you have an update from the product team?

Apologies. I still haven’t received a response from the product team. I will reach out to them again.

Hi @Jirapongse, Please can you chase your product team for a response, it's been almost a month since I raised this issue. Thanks

The product team has identified the root cause of the issue and is currently working on a fix. I will keep you updated.

I got the response from the product team.

The fix is planned for deployment to the production environment next weekend (14 February).

Hi @Jirapongse thank you for providing the ETA - Are you able to share the root cause?

This is the response from the product team.

We are still working on this issue, and we are getting the response properly in both QA and PPE environment, issue is with data that is populating when we match the quote data in Prod environment alone(permid.org). We will push the changes that we have done in QA and test the quote data. We will have to trigger and deploy the changes to production environment on the next weekend.

Hi @Jirapongse,

Can you check with the product team if the release was rolled out over the weekend? If so, I tested the same example I previously shared above and I am still getting different responses:

1.	"outputContentResponse": [ { "ProcessingStatus": "OK", "Match OpenPermID": " https://permid.org/1-5057820156 ", "Match OrgName": "Aroundtown SA", "Match Score": "100%", "Match Level": "Excellent", "Match Ordinal": "1", "Original Row Number": "2", "Input_LocalID": "1", "Input_Standard Identifier": "Ticker:ALCRE&&MIC:ALXP" } ]
2.	"outputContentResponse": [ { "ProcessingStatus": "OK", "Match Level": "No Match", "Original Row Number": "2", "Input_LocalID": "1", "Input_Standard Identifier": "Ticker:ALCRE&&MIC:ALXP" } ]

If not, when is the release scheduled to be rolled out?

Thanks.

Let me contact the product team to verify it.