Submit a ticket
Welcome
Login

Troubleshooting

On this page, you can check more information about possible errors on Oneflow for Salesforce.


Common Errors

Couldn't connect to Oneflow, when activating the Salesforce extension in Oneflow you will be given an API token. 
This token allows the Oneflow for Salesforce application to connect to Oneflow. Go to settings in Oneflow to enable the Salesforce extension.

Cause: Oneflow for Salesforce API TOKEN is missing or no longer valid. 

Solution: Make sure "Oneflow for Salesforce" is set up, by navigating to the "Configuration Page" on Oneflow App (only visible to users with "Oneflow Administrator" permission set.) and following the steps shown on the "Get Started" guide. 

For more information on how to set up our application, follow the steps shown here.


#36 Couldn't find a matching Oneflow user (email) for the Salesforce user. Please contact your Salesforce administrator. (Error #006)

Cause:  Salesforce User Email and Oneflow User Email are different

Solution: Make sure there is a registered Oneflow User with the same email address as the current Salesforce User seeing this error. 


Request to /agreements/ failed with 400 because Participant with duplicate email XXX@oneflow.com

Cause: At least 2 Participants have the same email.

Solution:  When creating a contract, please ensure that all emails shown on the participants' list are different. 

Also, ensure that neither of the participants has the same email as the Salesforce User creating the contract.


Request to /agreements/ failed with 400 because Participant with duplicate phone number XXX-XXX-XXXXX

Cause: At least 2 Participants have the same phone number.

Solution:  When creating a contract, please ensure that all phone numbers shown on the participants' list are different.


Missing access rights on Opportunity. XXX (Error #018)

Cause: Salesforce user does not have permission to read field XXX on Opportunity object.

Solution:  Give permission to read access permission to the user or go to "Data Fields Configuration" on the Configuration page to uncheck field XXX from Opportunity if you don't wish to use it on contract creation. 

Check our article about Permissions on Oneflow for Salesforce to know more.


Errors related to Product Mapping

One of the previously mapped fields does not exist (might have been deleted) or is misspelled or is missing namespace.

A user trying to create the contract does not have access to the field specified by the error message.

Product Mapping Custom Settings is missing.

Product Name on Product Mapping configuration is mandatory.



Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.