For a deeper look into our World Check One API, look into:

Overview |  Quickstart |  Documentation |  Downloads

question

Upvotes
Accepted
115 2 5 10

Issue with the end point /screeningRequest

There seems to be an issue with the end point /screeningRequest. Any requests to pilot are totally frozen and not working. The production is also working very slow. It is affecting all our customers.

Just after run aml check for case (by /screeningRequest) we check ModificationDate of case. When modificationDate is changed we know that aml check been has done for the case. But right now modificationDate is not changing which means that screeningRequest is not working for existing cases. Is there any known issue around this?

world-checkworld-check-one
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Hello @devops.kyc,

Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query? If yes, please click the 'Accept' text next to the reply. This will guide all community members who have a similar question. Otherwise please post again offering further insight into your question.

Thanks,

AHS

Upvotes
Accepted
115 2 5 10

Its working again. Looks like it is a capacity / load issue, which is re-occuring.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
1 0 0 0

We also are getting similar issues, our cases were stucked because cases on WC1 side are not screened even after 1 hour.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
31 0 0 0

Same here.
Is there an endpoint where we can check the status in such cases?

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
115 2 5 10

Our pilot started working 3 hours back but now it is again down.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
1.3k 4 1 2

@devops.kyc

This is currently under investigation and we will provide you an update soon.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
1.3k 4 1 2

@devops.kyc @s.kiselev @DSP

There was an issue with the async screening API call but I have been informed that it was resolved at 1:30 AM IST, can you check and confirm if you are still facing any issues with the endpoint?

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
115 2 5 10

@Mehran Khan it was working till noon today but the issue has again cropped up.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
1.3k 4 1 2

@devops.kyc

Thanks for the comment, I have informed the concerned team, will get back with the updates.

Please do share some timestamps from when the issue resurfaced.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
1.3k 4 1 2

@devops.kyc

To add, please also share a few caseSystemIds of the impacted cases so that the team can investigate it in depth.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

@devops.kyc,

Following up on the above comment - Could you please share a few case system ids for further investigation?

Upvotes
1.3k 4 1 2

@devops.kyc

Thanks for the comment, we will monitor it further. Please let us know if you experience this again.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

@Mehran Khan there is a similar outage yesterday and today

can you please fix?

it is business critical

thanks.

Upvotes
31 0 0 0

Hi, it seems this issue resurfaced again.
More specifically, I don't get the 'SCREENED_CASE' audit event, even after a few hours.
Here are two caseSystemIds: 5nzbfkdmfcnu1fasff1bx1ouq from this morning and 5nzbfqankw2o1fasn0svcslty which is more recent.
Could you have a look at it?
This is occurring in the worldcheck one pilot environment.
Thanks..

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
115 2 5 10

We are also seeing this issue again today. It started with pilot but also started to appear on production. We are still impacted. Anyone else having issues on production account as well.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
115 2 5 10

@Mehran Khan We are again seeing this issue today on pilot. Can somebody from refinitiv side? This is urgent as queue build up on pilot affects our production microservice as well and impacts all our customers.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvotes
115 2 5 10

We have seen repeated issues with pilot during our internal testing as reported by our QA team. Can someone from Refinitiv, please look into this. Thanks

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Upvote
115 2 5 10
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.