This page documents potential issues encountered by integration users that are either obscure or frequently asked about. If an error message is not listed here, please search in Salesforce’s documentation to determine whether the error is Salesforce-related or Chargify-related, or peruse our Salesforce FAQ for general questions about the integration.
The Chargify Logs object will collect certain errors that occur from the integration’s natural sync.
Sometimes when a webhook is sent from Chargify to Salesforce, there is no associated Opportunity currently in Salesforce. This error is intended to be an informational message to let you know that a particular webhook was not used to update a subscription because no associated Salesforce Opp exists. If you are receiving this message, please inspect your integration to understand why the Opportunity is missing.
As an example, let’s say a subscription was created in Chargify but the webhook failed to send to Salesforce. Later, a billing date change is made in Chargify. The billing date change webhook is sent to Salesforce for that subscription, but there is no corresponding subscription ID attached to an Opportunity in Salesforce. Therefore, this error is returned.
Webhooks sent from Chargify to Salesforce to sync subscription data can return particular errors that will be displayed in the Chargify webhook panel.
When all webhooks sent by Chargify to Salesforce are returning a 500 in the webhook panel and your account is on a free trial, it’s possible that your Salesforce license with the Chargify integration may be expired.
- Go to ‘Setup’
- Click ‘Installed Packages’
- Look for the ‘Chargify’ installed package and check the expiration date
If the license is expired, please contact firstname.lastname@example.org to purchase one.
It’s possible that the webhook endpoint entered inside Chargify is incorrect, if there are no associated error logs in the Chargify Logs. The URL associated with Salesforce should be comprised of two parts:
- From Salesforce:
- Click Setup
- From the Quick Find box, search for “Site” and click on the link. It will be under the “Develop” section
- Click on the “Site Label” for the Chargify Site that was created
- Copy the site’s “Domain Name”. An example would be
- To that domain name, append this text to the end:
The full URL will resemble this:
Watch out for duplicate slashes in the URL. Additionally, all live Chargify sites must be using HTTPS in the webhook URL rather than HTTP.
Please verify that only the subdomain is entered in the “subdomain” field on the Chargify Configuration page, rather than the full Chargify URL. For example, if your Chargify URL is https://subdomain.chargify.com, the Chargify Configuration page should look resemble the screenshot below:
This error can occur when attempting to click the “Resync Subscription” button on the Opportunity when the following setting is configured under Chargify Configuration:
- Update existing Opportunity on Chargify Product change
When a product change occurs, the original Opportunity’s subscription ID will be wrapped in parenthesis to signify that it should no longer be updated. Please search for the subscription ID in Salesforce and attempt to resync the active Opp; it will not have parentheses around the subscription ID.
Each Visualforce page makes an API call to Chargify to retrieve the requested information and display it inside Salesforce. If this error is being returned when interacting with a Visualforce page, such as the invoices and transactions pages, it’s possible that there is not enough information in the Opp to complete the API call.
Please ensure that the following requirements are met on the Opp:
- It contains a subscription ID and Chargify subdomain
- The subdomain is spelled correctly
- The subdomain matches one that is configured as part as the integration
On step 3 of the Salesforce installation, when clicking “Edit Assignments” on the Site Guest User to grant them the “Provide Permissions to Chargify” permission set, this error may be returned.
The cause is that the Site associated with the Site User may be inactive. Please follow these steps:
- Click ‘Setup’
- In the Quick Find box, type “Sites” and click the appropriate link; it will be under Build > Develop
- Click “activate” on the site created in the previous step of the install process.
If you have enabled the Salesforce Summer 20’ release early and are experiencing 500 errors with your webhooks this workaround will correct the issue.
When you experience such error, please follow the below steps:
- Create new Permission Set granting “Read” access to Price Book object
- Assign newly created permission set to the Guest Site User
Detailed step by step instruction:
Create new Permission set with “Read” access to Price Book
You have successfully created the “Access to Price Book for Guest User” permission set. Now lets assign it to the Guest Site User
Assign newly created permission set to the Guest Site User
You have successfully assigned the permission set to the Guest User. On the list of Permission Set Assignments for the Guest Site User you should now see the newly assigned “Access to Price Book for Guest User” (like in the screen above)
The integration is ready for retest: you can either resend the failed webhooks from Chargify to Salesforce, or trigger new webhooks by creating a new Subscription. Now the Webhooks “payment_success” and “statement_settled” should be processed successfully in Chargify and Salesforce.