The number of Pre-Verify results does not match the number of documents that were sent for verification.
Wednesday, November 16, 2022 at 03:32pmHello,
I received an error message on trying to create a OneSpan package with the error code: "The number of Pre-Verify results does not match the number of documents that were sent for verification."
I don't have access to the request that was made, but it's one of many that are sent out successfully every day. I was wondering what cases could potentially cause this error message — I can't find anything in the documentation, and one forum post mentions "ADA" which I'm not using.
Thank you!
Reply to: The number of Pre-Verify results does not match the number of documents that were sent for verification.
Wednesday, November 16, 2022 at 04:29pmHi Abbie,
Thanks for your post! Is the issue consistent, or it's gone with a retry mechanism? Do you have access to this document so that we can reproduce the error?
According to the error message, it says that the actual detected document number didn't match the JSON payload. Hence on top of my head, I think the issue could either be related to the document itself, or related to how the raw request was built.
Duo
Reply to: The number of Pre-Verify results does not match the number of documents that were sent for verification.
Wednesday, November 16, 2022 at 04:33pmHi Duo,
It's a one-off issue for now, but I'm trying to document all the potential errors from OneSpan so we know how to handle them if they pop up again :) I don't have access to the document, and our other requests with a variable number of documents are all successful — when I was first testing that, the error was "Number of uploaded files does not match number of documents specified in package," which is similar but doesn't mention the "Pre-Verify", so I was wondering what the Pre-Verify results might be referring to.
I found another forum post that mentions a corrupted pdf — maybe this could be the issue?