This article lists the error messages the Salesforce integration can produce, what causes each one, and how to resolve it.
Supported Flows
The errors in this article are grouped by the flow that produces them:
Authentication
Account TO iPaaS.com (Salesforce → iPaaS.com)
Account FROM iPaaS.com (iPaaS.com → Salesforce)
Contact TO iPaaS.com (Salesforce → iPaaS.com)
Contact FROM iPaaS.com (iPaaS.com → Salesforce)
General platform errors
Where these errors appear
All integration errors surface in the iPaaS.com Dashboard under Integration Monitoring → Error Logs. Each entry records the message, the affected record, and the time it occurred. Start there when a sync does not complete as expected.
A note on what is and is not an error: some records are skipped by design rather than failed. For example, a Salesforce contact without an associated account, or an address that is not the primary shipping address, is quietly passed over so it does not create incomplete data on the other side. These skips are not errors and do not appear in the Error Logs. The messages below are genuine failures or warnings that the integration raises.
All of the messages below are produced by the integration's processing logic. They are not editable in the mapping configuration.
Authentication
These apply to the connection as a whole and can affect any flow.
Refresh token missing — re-authentication required
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.
Cause: The OAuth connection to Salesforce is incomplete. This happens when the Salesforce Connected App credentials (Consumer Key and Consumer Secret) are missing, or when the authorization to Salesforce was never completed or has expired.
Resolution: Re-authenticate from the Subscription Settings page in iPaaS.com. Confirm that the Consumer Key and Consumer Secret are present and correct, then complete the Salesforce authorization so a valid token is issued.
Account TO iPaaS.com (Salesforce → iPaaS.com)
Errors raised while sending a Salesforce account into iPaaS.com as a company.
Salesforce rejected the new account
Salesforce rejected the new account.
Cause: Salesforce returned one or more errors when the integration attempted to create the account. This is typically a missing required field, a field value that fails a Salesforce validation rule, or insufficient permissions on the connected Salesforce user.
Resolution: Open the Error Logs entry to see the specific reason Salesforce returned. Correct the offending field value, adjust the Salesforce validation rule, or grant the required permission, then allow the record to sync again.
Duplicate account detected
DUPLICATES_DETECTED. This means that the record sent in the request already exists in Salesforce.
Cause: A Salesforce duplicate rule matched the account being created, and no collision-handling method was selected in the mapping configuration. Without a collision-handling method, the integration cannot decide whether to link to the existing record, so it reports the duplicate instead.
Resolution: Select a collision-handling method in the iPaaS.com mapping configuration so the integration can link to the existing Salesforce record, or reconcile the duplicate directly in Salesforce.
Account FROM iPaaS.com (iPaaS.com → Salesforce)
Errors raised while writing an iPaaS.com company back to a Salesforce account.
Account Id missing for update
Account Id is null or empty and it is required for the account update.
Cause: The integration tried to update a Salesforce account but could not determine which Salesforce record to update, because no Salesforce Account Id is linked to the iPaaS.com company.
Resolution: Make sure the company has already been synced to Salesforce so the link to a Salesforce account exists. A record must be created in Salesforce before it can be updated from iPaaS.com.
Salesforce API call failed
Error calling SalesForce (Http Code: {code})
Cause: A call to the Salesforce API returned a non-success HTTP response. This can be transient (a temporary outage or timeout) or the result of a Salesforce-side condition such as an API limit.
Resolution: Allow the integration to retry. If the error persists, check the Salesforce service status and your org's API limits. If neither explains the failure, contact iPaaS.com Support.
Contact TO iPaaS.com (Salesforce → iPaaS.com)
Errors raised while sending a Salesforce contact into iPaaS.com as a customer.
Salesforce rejected the new contact
Salesforce rejected the new contact.
Cause: Salesforce returned one or more errors when the integration attempted to create the contact. This is typically a missing required field, a value that fails a Salesforce validation rule, or insufficient permissions on the connected Salesforce user.
Resolution: Open the Error Logs entry to see the specific reason Salesforce returned, correct the field value or permission, then allow the record to sync again.
Contact not linked to an account
AccountId is null or empty on the iPaaS Customer record, and it is required for linking the contact to the account.
Cause: The contact must be linked to a company in iPaaS.com, but the related account is not present on the iPaaS.com customer record.
Resolution: Sync the related account first so the company exists and the link can be made, then allow the contact to sync.
Related account not found in Salesforce
Could not locate account by Id: {id} in Salesforce. Account must exist in Salesforce before attempting to create the contact under it.
Cause: 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.
Unable to link contact by email
Unable to dynamically link to existing Salesforce customer using email address. This may result in duplicate customer records.
Cause: The integration links contacts to existing customers by email address to avoid duplicates. It could not match the 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. If a duplicate was created, reconcile the two records.
Duplicate contact detected
DUPLICATES_DETECTED. This means that the record sent in the request already exists in Salesforce.
Cause: A Salesforce duplicate rule matched the contact being created, and no collision-handling method was selected in the mapping configuration.
Resolution: Select a collision-handling method in the iPaaS.com mapping configuration so the integration can link to the existing record, or reconcile the duplicate directly in Salesforce.
Contact FROM iPaaS.com (iPaaS.com → Salesforce)
Errors raised while writing an iPaaS.com customer back to a Salesforce contact.
Salesforce API call failed
Error calling SalesForce (Http Code: {code})
Cause: A call to the Salesforce API returned a non-success HTTP response, either transient or the result of a Salesforce-side condition such as an API limit.
Resolution: Allow the integration to retry. If the error persists, check the Salesforce service status and your org's API limits, then contact iPaaS.com Support if it is not resolved.
General platform errors
These can occur in any flow when the iPaaS.com API itself returns an error during a read or write.
iPaaS.com API error
An iPaaS.com API error was returned.
Cause: The iPaaS.com API returned an error while reading or writing a customer or company during the sync.
Resolution: Open the Error Logs entry for the detail. If it points to a correctable data issue, fix the record and allow it to sync again. Otherwise, contact iPaaS.com Support.