When there are errors with the Recurly to Salesforce sync, the API will attempt to re-sync the failed data automatically. For example, if an invoice is unable to be synced, the integration will attempt to re-sync when it runs next. These messages will appear in the Recurly Logs tab in the Recurly for Salesforce application.
To run a report about these errors, a folder called "Recurly Reports" has been created in Reports and Dashboards within Salesforce. The report called "Recurly Error Logs" within this folder provides reporting on errors from Recurly to Salesforce. This is the first place to check when you find errors in your sync process.
As of version 2.39, the progress of each sync batch is recorded in a log. The Recurly Log captures how many records of each type were successfully created or failed.
NOTE: If you installed a previous version of the package and were upgraded to 2.39, you may need to alter the layout of the Recurly Logs object to see the data which is passed in the Sync Stats Record.
When data fails to sync between Salesforce and Recurly, the user who edited the record inside of Salesforce will receive an email with information on why the sync failed.
You are able to add Force.com customization on top of Recurly custom objects within Salesforce. However, these customizations will not be supported by Recurly as every merchant will require different triggers, workflows, and customizations in order to integrate Recurly data into their business process.
Below you will find some common issues and the solutions for them:
Recurly accounts are not being linked to Salesforce standard accounts.
Check the Recurly Admin tab and make sure that you have linking to Salesforce accounts enabled.
If you are still experiencing issues, ensure that the field on which you link Salesforce and Recurly accounts is populating correctly on Recurly accounts.
I can't add my Recurly API keys to the API Settings tab in Salesforce.
Check the character length of your Recurly subdomain (subdomain.recurly.com). The Salesforce character limit for a Recurly subdomain is 25 characters. An error will occur when trying to connect Salesforce to Recurly via the API keys if your subdomain exceeds this length.
Salesforce accounts are not being created in my org when Recurly accounts are created.
Check the Recurly Admin tab to make sure that you have the option to create Salesforce accounts enabled.
I am missing Recurly data in my Salesforce org.
There could be a number of reasons for this. Follow these steps:
My users can't see data.
This is either due to:
I can't uninstall the package.
Salesforce offers duplicate management through data.com functionality. While the ability to report on and block duplicates is great for your users, it can cause issues for API integrations. In order to ensure that your data can sync and update properly from Recurly, we urge you to take the following steps:
- Fully exclude the user running the sync, including the "Recurly for Salesforce" user and any updates from our system, from triggering the data.com rules
- Manually exclude any updates to fields related to the Recurly sync
- For your initial sync, deactivate your data.com rules completely. Since Recurly needs to access your standard accounts for linking, deactivating your data.com rules is the best way to ensure that all of the data is synchronized properly.
If you do not follow these steps, Recurly cannot guarantee that all of your data will be synced to Salesforce or linked correctly to your Salesforce accounts.
If you require further support, please contact Recurly Support and we will be happy to assist you.
Please be sure to mention which version of the package you are using (this is available on the Recurly Admin screen).
Updated over 1 year ago