function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
zapierzapier 

Increased instances of ECONNREFUSED Errors

Since September 5th, we have been seeing a large increase in the number of requests that fail to connect to the Salesforce API, due to ECONNREFUSED socket errors. A month later and we're still seeing hundreds of these requests failing each hour.
Our analysis reveals that it's no one particular organisation's subdomain or any particular API endpoints that are failing to respond to our connections.

Our question: Have there been any changes in the last month that would make connecting to the Salesforce API fail so often? Perhaps changes to firewalls, throttling limits, etc?

Any assistance with this matter would be greatly appreciated.
Thanks, Zapier Integrations Team.
SwethaSwetha (Salesforce Developers) 
Hi Team,
Can you include the complete error message?
Are you seeing this behavior across all orgs- prod/sandboxes? Is this an intermittent issue? Can the issue be reproduced via third-party tools like postman?

See https://www.salesforceben.com/salesforce-winter-23-release-date-preview-information/ about the timelines for Winter'23 release on your orgs. 

Thanks
zapierzapier
Hey there, It looks like you’ve emailed Zapier Support directly. This email address is no longer in service and any further replies on this email thread will not be monitored. Please use our contact form (https://zapier.com/app/get-help?utm_source=zapier&utm_medium=email&utm_campaign=zen-gbl-ret-nur-zendesk_direct_email_redirect) to get in touch with Zapier Support. This helps route your ticket to the appropriate team and surfaces relevant resources from our Help Center (https://zapier.com/help) and Community (https://community.zapier.com/) which may help you to solve your question even faster. Thanks! P.S Think you might be experiencing an outage? Check our status page (https://status.zapier.com/).
zapierzapier
We have a large user base, and we are seeing the error occurr thousands of times an hour.

I've included an example below, but we see the same error show up often when we make connections to any [customer].my.salesforce.com urls, initiated from the standard Python and JavaScript HTTP libraries.

ECONNREFUSED means no connection is being established to Salesforce at the network layer, so there's no diagnostic or status information sent back to us. 
Unhandled error: FetchError: request to https://[CUSTOMER-ORGANISATION].my.salesforce.com/services/data/v46.0/query?q=SELECT%20Id%20FROM%20Account%20ORDER%20BY%20CreatedDate%20Desc%20LIMIT%202000 failed, reason: connect ECONNREFUSED 15.236.216.240:443 What happened: Starting GET request to https://[CUSTOMER-ORGANISATION].my.salesforce.com/services/data/v46.0/query request to https://[CUSTOMER-ORGANISATION].my.salesforce.com/services/data/v46.0/query?q=SELECT%20Id%20FROM%20Account%20ORDER%20BY%20CreatedDate%20Desc%20LIMIT%202000 failed, reason: connect ECONNREFUSED 15.236.216.240:443 FetchError: request to https://[CUSTOMER-ORGANISATION].my.salesforce.com/services/data/v46.0/query?q=SELECT%20Id%20FROM%20Account%20ORDER%20BY%20CreatedDate%20Desc%20LIMIT%202000 failed, reason: connect ECONNREFUSED 15.236.216.240:443 at ClientRequest.<anonymous> (:censored:9:d1ba0cf2aa:/node_modules/zapier-platform-core/node_modules/node-fetch/lib/index.js:1461:11) at ClientRequest.emit (events.js:314:20) at ClientRequest.EventEmitter.emit (domain.js:483:12) at TLSSocket.socketErrorListener (_http_client.js:427:9) at TLSSocket.emit (events.js:314:20) at TLSSocket.EventEmitter.emit (domain.js:483:12) at emitErrorNT (internal/streams/destroy.js:92:8) at emitErrorAndCloseNT (internal/streams/destroy.js:60:3) at processTicksAndRejections (internal/process/task_queues.js:84:21)
We can also retry requests within a second and see a successful connection and correct 200 HTTP response, indicating this issue is intermittant. Our network traffic can originate from arbitrary IP addresses in the AWS US-East region. Could there be a possible reason that some initiating adresses are getting blocked while others are permitted through?