Closed rosskevin closed 2 months ago
I'll note that the custom field is unique, but was not set as such. I have now added that and hope that it makes responses more timely.
I do think the lack of proper status 408 yielded from SDK in a timeout situation is a bug and should be addressed.
Hi @rosskevin Thanks for informing! Please forward the issue details and SDK configuration samples to support@zohocrm.com and we'll take things forward.
@raja-7453 no thank you. Last time I did that, it was front line support sending me to basic articles. This is an SDK bug, and it should be dealt with directly in the project that houses the code, or a developer support issue tracker.
I shouldn't have to spend that much time contributing information to help solve a common code problem.
Since this is because of the configured timeout, it has been handled considering it as an SDK-exception instead of a response from the API (which is the one that could return the status code).
So, from this 6.0.0 version, it will be thrown as Error response : Operation timed out after 2000 milliseconds with 0 bytes received if timeout occurs.
We are receiving numerous unknown responses from the SDK. It is totally unknown, sometimes it works, sometimes it doesn't. I tried logging the response object, but it is simply empty:
The code running this:
These are the sdk logs for that call:
Why am I receiving timeouts when attempting to search and get a single record by custom field code? Why isn't this an http status
408
?