One of the many reasons to take payments in Salesforce is to take advantage of Salesforce’s automation and customization. That being said, there are a few considerations and troubleshooting measures you can take to ensure your solution works flawlessly.
- Custom Automation (Flow, Process Builder, Workflow Rules, or Apex), Validation Rules, and Required Fields can prevent a Chargent Order from saving properly after a transaction occurs, which can prevent the Transaction from being properly saved to the parent Chargent Order.
- We recommend adding a time delay for all after-save record-triggered flows to avoid conflicts when committing records to the database. For more information, see Add a Delay to a Salesforce Record-Triggered Flow.
- Recurring transactions run in a batch. In this case, an error would be visible in the Apex Jobs in Salesforce. An email related to the error will also be sent to the Chargent Admin Email Address as configured in the Chargent Settings Tab.
- Chargent also includes a custom object called Email Notification. Some Email Notification records will appear as Unresolved Transactions in your Chargent app and can help you troubleshoot any issues. Once your issue is resolved, you can use the Unresolved Transactions tab to create the transaction records successfully.
- Some Automation or Validation Rule problems can result in duplicate transactions, so ensure you test any custom solutions in a Sandbox prior to deployment.
See Also
Troubleshooting Your Batch Apex Jobs
How do I receive Email Notifications as a Chargent Admin?
Understanding Unresolved Transactions
