[BUG] ...SocketTimeoutException:Read timed out

[adrianann]

Describe the bug Hi, When I'm trying for the first time (after a long period of not creating customers/orders like one day) to syncronize a customer or an order (I've implemented the part with syncing orders), I'm receiving in the callback from ServiceCloud a timeout exception. The Contact is saved in Service Cloud, but when it returns in Commerce cloud it does not save the Salesforce Account Id and Salesforce Contact Id because the result has "SocketTimeoutException:Read timed out" as a response. The others that I'm entering after the first one are working as they should without timeout.

To Reproduce Steps to reproduce the behavior:

1. Go to Create from storefront a new customer (first record that day) and create one customer
2. Checking in Commerce cloud in BM for that customer it has null values for Salesforce Account Id and Contact id fields and in Salesforce response text the value "Tue, 16 Nov 2021 09:20:44 GMT: Status 0 (Read timed out): SocketTimeoutException:Read timed out"

Expected behavior The values in Salesforce Account Id and Contact id fields should be filled with the values from Service Cloud and in the response text should be something like "Tue, 16 Nov 2021 10:33:29 GMT: Successfully exported to Salesforce Org during the "login" logic."

Your local environment details:

• Node version (node -v): [v15.2.1]
• NPM version (npm -v) [v7.0.8]
• SFDX version (sfdx -v) [sfdx-cli/7.115.1 win32-x64 node-v14.17.5]

Your remote environment details:

• Salesforce B2C Commerce version: [e.g. 21.10]
• Salesforce Core version: [e.g. 52]

[olegforce]

I had the same SocketTimeoutException issue on the development environment but was told there is no such issue on the production environments. Can you please confirm you see this one on production or development one?

[adrianann]

It's in a dev enviroment indeed. So you went with the error in production and in production didn't appeared?

Thanks for the response

[olegforce]

I didn't go personally to production but heard from the folks who went, that such an issue occurs only in the development environment due to the nature of dev environments. Maybe someone else will be able to confirm this statement.