/
ERROR 137: Salesforce Timeout

ERROR 137: Salesforce Timeout

Problem

Users press Sync Now button and the sync fails.

Error log example

[22-04-25 23:33:49][INFO ][0x170617000] - integrateAfterSync: skipped due to sync failure (137)
[22-04-25 23:33:49][ERROR][0x170617000] - sfsub->sync() failed (137)

Solution

It is a request timeout error, meaning Pulsar sent the query over to Salesforce and is waiting for a response back from the server. If Pulsar does not receive a response from Salesforce before a standard interval (per network settings per operating system), it times out and requires the user to run the sync now action again.

This error happens in Sandboxes much more than in Production instances because of the inherent performance differences. Also, your network quality can affect performance.

Train the users about this particular error and train them to press Sync Now again and find a better internet connection, if possible.

 

Related content

ERROR 220: Relationship Sync Failure
ERROR 220: Relationship Sync Failure
More like this
How do translations work in Pulsar?
How do translations work in Pulsar?
Read with this
ERROR: Server operation too large (error code 1150)
ERROR: Server operation too large (error code 1150)
More like this
ERROR: Not Found or ERROR: Invalid Type
ERROR: Not Found or ERROR: Invalid Type
More like this