Byte

Notifications and race conditions

0 votes
I am responding to certain inbound notification events (i.e. DOCUMENT_SIGNED and SIGNER_COMPLETE) by making outbound calls using the SDK. For instance, when I get a SIGNER_COMPLETE notification, I make a call out to eSignLive to verify the status of all signers and retrieve the signed documents. It appears that when I make the outbound call to eSignLive that the status information has not yet been updated and I get the old status. It seems like a classic race condition. If I check manually a few minutes later I get the correct status. Should I wait for a few seconds before making the outbound call so that I get the correct data? If so, what is the recommended delay? I'm testing in the sandbox environment.

Reply to: Notifications and race conditions

0 votes
I don't know if there is an expected delay. I will check on this, in the morning. Have you noticed a pattern to when you're getting the proper result with a manual call? Is the incorrect SDK pull a consistent issue? Or is it intermittent?

- Michael

Director, Partner and Developer Technologies, OneSpan

Facebook - Twitter - LinkedIn


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off