Hi Martin :

Chris reported this issue. When he searched for "Hydro Energy v. Spain" under Global Search, he is getting an error message with the following URL: https://app.investorstatelawguide.com/DisputeDocuments/DisputeAllDetails?dis=Wk21nmb-fNY%3D.

Also, as shown below, data is not displayed when users click on the Global Search results of Hydro Energy v. Spain whersaa you access the same dispute via Disputes & Dispute Documents, it works.

Global search error (17-Jan-23).mp4 4.01 MB • Download

Please add it to unplanned/critical.

Thanks,

Paul

Hi Harsh ,

Please see Paul 's comment and video above. We have encountered a similar issue before, but I cannot locate it.

I have created task https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/2474 to track this.

Thanks,
-Martin

Hi Paul ,

I have checked the Global Search issue in app.islg and it is working fine. Can you please check again ?

Also, for this URL : https://app.investorstatelawguide.com/DisputeDocuments/DisputeAllDetails?dis=Wk21nmb-fNY%3D. - We decrypted last Id (Wk21nmb-fNY%3D) and got the value 0.

I feel the URL is wrong. Can you please check how you will get this URL ?

Cc : Martin  

Hi Harsh :

This is the original screenshot we received below, and I still get the same error message when I copy and paste it. If you decrypt the last ID and get 0 for value, how can a subscriber get there in the first place?

image.png 111 KB • Download

Martin : you were also copied in Chris' original email yesterday. Compared to my video above, now, I can see the dispute details appearing if I click through Global Search results. Has something changed?

Thanks,

Paul

Hi Harsh ,

What is your theory on why Chris and Paul encountered this issue yesterday, but it is not happening today?

Could it be related to an issue with indexing, or perhaps a SQL job that did not complete fully?

Was any code updated on app.islg that could have affected this?

Thanks,
-Martin

Hi Paul and Martin ,

We haven't changed in code. Might be there is possibility that Chris was checked during Indexing was generating. As the Dispute document data is coming from Indexing.

Hi Paul ,

At this point, since we're unable to replicate this error, we are not 100% certain on how it occurred.

One thing that would help us troubleshoot would be to understand how and where Chris was able to get the false URL: https://app.investorstatelawguide.com/DisputeDocuments/DisputeAllDetails?dis=Wk21nmb-fNY%3D. 

As a side note, the team and I discussed this morning and agreed that the error message should be better handled and more graceful.
I have created backlog item https://dev.azure.com/tologix/ISLGRebuild/_workitems/edit/2486 to address this specific problem. The effort should be less than 4 hours. Please prioritize accordingly.

Thanks,
-Martin

Indexing is showing the dispute information now.