question

Upvotes
Accepted
LarryT avatar image
322 ●11 ●16 ●21

I am getting an error “Failed to save case to WC1. Status Code: 404” when attempting to screen custom objects

It worked fine in our UAT environment but is failing when we move to production

#technology#productworld-checkscreeningscreening-apiscreenerrisk
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.

Jirapongse avatar image   Jirapongse

@LarryT

Hi,

Thank you for your participation in the forum.

Is the reply below satisfactory in answering your question?

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

wasin.w avatar image   wasin.w

Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.

Thanks,


AHS


1 Answer

· Write an Answer
Upvotes
Accepted
hannah.quinn01 avatar image
151 ●1 ●1 ●3

In UAT were you connected to your production instance of World-Check or a Pilot Instance of World-Check? 404 suggests that something is incorrect in the custom mapping which is preventing the case from being created in World-Check. If it worked fine in UAT then the most likely reason for this is that the Group ID you specified in production is incorrect. Group Ids are unique to each World-Check environment so please check the IDs from your production World-Check and then check the mapping in your custom flows/apex is referencing the correct ID.

There is information on how to find the group id on the developer portal.

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.