question

Upvotes
Accepted
322 11 15 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

#technologyworld-check#productscreeningscreening-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.

1 Answer

· Write an Answer
Upvotes
Accepted
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.