Overview
This article catalogs the error messages the Salesforce integration can record in the iPaaS.com error logs. Each error carries a stable code you can search for on this page (use Ctrl+F / Cmd+F), the message text as it appears in the logs, what causes it, and how to resolve it. Integration errors appear in the iPaaS.com Dashboard under Integration Monitoring → Error Logs, where each entry records the message, the affected record, and the time it occurred.
Some records are skipped by design rather than failed — for example, a Salesforce contact without an associated company, or an address that is not the primary shipping address, is passed over quietly so it does not create incomplete data on the other side. Those skips are not errors and do not appear here.
Several resolutions below refer to your Managed Integration Service Provider (MiSP) — the party responsible for your integration's mappings, connection credentials, and reconciling records between Salesforce and iPaaS.com. If your organization manages its own integration, that responsibility is yours.
iPaaS.com categorizes errors by families. You can learn more about that categorization at Understanding iPaaS.com API Error Codes.
Supported Flows
The errors in this article come from these flows:
Authentication
Account FROM iPaaS.com (iPaaS.com → Salesforce)
Contact FROM iPaaS.com (iPaaS.com → Salesforce)
Contact TO iPaaS.com (Salesforce → iPaaS.com)
General (can occur in any flow)
Error Collection
Authentication
These apply to the connection as a whole and can affect any flow.
Refresh token missing
SFDC-AUTH-1001 - Refresh token value is either null or empty and is required for obtaining an AccessToken. Please re-authenticate from the Subscription Settings page in iPaaS.
Description: The OAuth connection to Salesforce is incomplete. The stored refresh token is missing, which happens when the Salesforce authorization was never completed or has been cleared.
Resolution: Re-authenticate from the Subscription Settings page in iPaaS.com. Confirm the Consumer Key and Consumer Secret are present and correct, then complete the Salesforce authorization so a new token is issued.
Access token refresh failed
SFDC-AUTH-1002 - Unable to obtain a new AccessToken by using the RefreshToken. Error: {error}. Error Description: {description} Please delete AccessToken and RefreshToken from the Subscription Settings page in iPaaS and re-authenticate.
Description: Salesforce rejected the stored refresh token when the integration tried to obtain a new access token. This usually means the token has expired or been revoked in Salesforce. The specific reason Salesforce returned is included in the message.
Resolution: Delete the AccessToken and RefreshToken from the Subscription Settings page in iPaaS.com and re-authenticate to Salesforce to issue fresh tokens.
Consumer Key missing
SFDC-AUTH-1003 - Unable to complete OAuth process in ProcessAuthorization. ConsumerKey is not specified in the subscription preset.
Description: The authorization could not start because the Consumer Key from your Salesforce Connected App is not set on the subscription.
Resolution: Enter the Consumer Key in the subscription's connection settings, then re-run the Salesforce authorization.
Consumer Secret missing
SFDC-AUTH-1004 - Unable to complete OAuth process in ProcessAuthorization. ConsumerSecret is not specified in the subscription preset.
Description: The authorization could not start because the Consumer Secret from your Salesforce Connected App is not set on the subscription.
Resolution: Enter the Consumer Secret in the subscription's connection settings, then re-run the Salesforce authorization.
OAuth token exchange failed
SFDC-AUTH-1005 - Unable to complete OAuth process in ProcessAuthorization. Failed to convert temporary code into a permanent token
Description: Salesforce did not return a token in exchange for the authorization code. This typically means the Connected App's Consumer Key, Consumer Secret, or callback configuration does not match, or the authorization code expired before it was used.
Resolution: Re-run the authorization from the Subscription Settings page. If it continues to fail, have your MiSP verify the Salesforce Connected App's Consumer Key, Consumer Secret, and callback URL.
Account FROM iPaaS.com (iPaaS.com → Salesforce)
Errors raised while writing an iPaaS.com company to a Salesforce account.
Account Id missing for update
SFDC-VALD-1001 - Account Id is null or empty and it is required for the account update.
Description: The integration tried to update a Salesforce account but no Salesforce Account Id is linked to the iPaaS.com company, so it cannot tell which record to update.
Resolution: Make sure the company was first created in Salesforce so the link exists. A record must be created in Salesforce before it can be updated from iPaaS.com.
Salesforce rejected the new account
SFDC-EXTN-1002 - Salesforce returned one or more errors while creating the account: {details}
Description: Salesforce returned one or more errors when the integration attempted to create the account — typically a missing required field, a value that fails a Salesforce validation rule, or insufficient permissions on the connected Salesforce user. The specific errors are included in the message.
Resolution: Review the errors in the message, correct the offending field value, adjust the Salesforce validation rule, or grant the required permission, then allow the record to sync again.
Unexpected account update response
SFDC-EXTN-1003 - Unexpected behavior after trying to update the Salesforce account with ID {id}. API response - {response}
Description: A successful account update returns no content from Salesforce. The integration received an unexpected response instead, which is included in the message.
Resolution: Review the response in the message and confirm whether the account updated in Salesforce. If it did not, allow the record to sync again. If this recurs, have your MiSP review the account's Salesforce validation rules.
Contact FROM iPaaS.com (iPaaS.com → Salesforce)
Errors raised while writing an iPaaS.com customer to a Salesforce contact.
Contact not linked to an account (create)
SFDC-VALD-1002 - AccountId is null or empty on the iPaaS Customer record, and it is required for linking the contact to the account.
Description: The contact must be linked to a company in iPaaS.com, but no related company is present on the iPaaS.com customer record.
Resolution: Sync the related company first so it exists and the link can be made, then allow the contact to sync.
Contact not linked to an account (update)
SFDC-VALD-1003 - AccountId is null or empty on the iPaaS Customer record, and it is required for updating the linked contact on the account in Salesforce.
Description: The contact update requires a linked company, but no related company is present on the iPaaS.com customer record.
Resolution: Confirm the customer is linked to a company in iPaaS.com, sync the company if needed, then allow the contact to sync.
Related account not found (create)
SFDC-NFND-1001 - Could not locate account by Id: {id} in Salesforce. Account must exist in Salesforce before attempting to create the contact under it.
Description: The integration looked up the account the contact belongs to and did not find it in Salesforce.
Resolution: Confirm the related account exists in Salesforce. The account must be present before the contact can be created under it — sync the company first if it has not yet reached Salesforce.
Related account not found (update)
SFDC-NFND-1002 - Could not locate account by Id: {id} in Salesforce. Account must exist in Salesforce before attempting to update the associated contact.
Description: The integration looked up the account the contact belongs to and did not find it in Salesforce while updating the contact.
Resolution: Confirm the related account still exists in Salesforce. If it was deleted or merged, reconcile the link in iPaaS.com before syncing the contact again.
Salesforce rejected the new contact
SFDC-EXTN-1004 - Salesforce returned one or more errors while creating the contact: {details}
Description: Salesforce returned one or more errors when the integration attempted to create the contact — typically a missing required field, a value that fails a Salesforce validation rule, or insufficient permissions on the connected Salesforce user. The specific errors are included in the message.
Resolution: Review the errors in the message, correct the field value or permission, then allow the record to sync again.
Unexpected contact update response
SFDC-EXTN-1005 - Unexpected behavior after trying to update the Salesforce contact with ID {id}. API response - {response}
Description: A successful contact update returns no content from Salesforce. The integration received an unexpected response instead, which is included in the message.
Resolution: Review the response in the message and confirm whether the contact updated in Salesforce. If it did not, allow the record to sync again. If this recurs, have your MiSP review the contact's Salesforce validation rules.
Account lookup failed during contact sync
SFDC-EXTN-1007 - Exception occured while attempting to locate Account by Id in Salesforce. Id = {id}. Exception: {message}
Description: The integration's lookup for the contact's related account did not complete. This is often transient. The underlying error is included in the message.
Resolution: Allow the integration to retry. If it persists, confirm the account Id is valid and that the connected Salesforce user has permission to read Accounts.
Contact TO iPaaS.com (Salesforce → iPaaS.com)
Errors raised while bringing a Salesforce contact into iPaaS.com as a customer.
Unable to link contact by email
SFDC-BIZL-1001 - Unable to dynamically link to existing Salesforce customer using email address. This may result in duplicate customer records.
Description: The integration links contacts to existing customers by email address to avoid duplicates. It could not match this contact to an existing record by email, so it proceeded and may have created a duplicate.
Resolution: Verify the email address on both the Salesforce contact and the matching iPaaS.com customer so they align. If a duplicate customer was created, reconcile the two records.
General (can occur in any flow)
These can occur in more than one flow whenever a Salesforce call fails or a duplicate is encountered.
Salesforce API call failed
SFDC-EXTN-1001 - Error calling Salesforce during {action}: {message} (HTTP status: {code})
Description: A call to the Salesforce API returned a non-success response. This can be transient (a temporary outage or timeout) or a Salesforce-side condition such as a validation rule, a permission issue, or an API limit. The Salesforce response and HTTP status are included in the message.
Resolution: Allow the integration to retry. If it persists, review the reason in the message and check the Salesforce service status and your org's API limits. If the message points to a validation rule or permission, correct it in Salesforce, then allow the record to sync again.
Duplicate record detected
SFDC-EXTN-1006 - DUPLICATES_DETECTED. This means that the record sent in the request already exists in Salesforce.
Description: A Salesforce duplicate rule matched the account or contact being created, and the mapping collection's Collision Handling Method is set to Error (or none), so the integration reports the duplicate instead of linking to the existing record.
Resolution: Open the mapping collection's settings and set the Collision Handling Method to a linking option — Remap and Link, Update and Link, or Update and No Link — so the integration links to the existing Salesforce record instead of erroring. Alternatively, reconcile the duplicate directly in Salesforce.
Batch run failed
SFDC-EXTN-1008 - Received an exception during the batch run for {action}. {firstException}
Description: One or more calls in a batched operation raised an error. The first underlying error is included in the message.
Resolution: Review the underlying error in the message and allow the batch to run again. Any record-specific errors listed elsewhere in this article explain the specific cause.
Duplicate details could not be read
SFDC-INTL-1001 - A duplicate was detected in Salesforce, but the details of the existing record could not be read to complete collision handling. Underlying error: {details}
Description: A Salesforce duplicate was detected while collision handling was configured to link records, but the integration could not read the existing record's details to complete the link.
Resolution: Allow the sync to run again. If it persists, reconcile the duplicate directly in Salesforce, or contact iPaaS.com Support at support@ipaas.com with the error details.