/cases/{caseSystemId}/ongoingScreening returns HTTP 423 Locked

AntonyDovgal

Hello,

We use World-Check v2 API in order to implement ongoing screening. Recently we noticed that method /cases/{caseSystemId}/ongoingScreening returns HTTP 423 Locked for some cases, but this response code is missing from the API docs. I tried reproducing it and got HTTP 204 instead, so the issue seems to be sporadic.

Could you help me understand what HTTP 423 means in this case and how to handle this response properly?

Thank you in advance.

ram_nitish

Hi @AntonyDovgal ,

Thank you for reaching out, we are looking into it and will get back to you shortly

Regards,
Ram.

ram_nitish

@AntonyDovgal,

HTTP 423 error typically occurs when multiple actions were being performed simultaneously on the same case.

Ex: If you're attempting to enable OGS on the case while it's still being screened, both actions may conflict, resulting in this error.
As a best practice, we recommend introducing a short delay between the two operations. Specifically, allow the screening process to complete before triggering the OGS enablement.

AntonyDovgal

Thank you very much for your quick response!

Is it possible to add this response to the API docs?

Thank you again.