Chargent Auto-Renewal Bug Report
VIDEO TRANSCRIPT | Recorded: 2025-08-27 | Verify against current system state
Abstract¶
Bug report documenting a critical Chargent auto-renewal failure. A test account's recurring payment was processed successfully through Braintree, but the Salesforce flow failed to create a new order due to a price book mismatch. The member was charged but their membership wasn't renewed. This issue requires investigation into price book configuration and error handling.
Key Procedures¶
- Create test account with auto-renewal
- Set recurring payment date to past to trigger processing
- Monitor overnight batch processing (runs at 3am)
- Check for new order creation and dues paid through update
- Review error logs for flow failures
- Verify transaction in Braintree
Notable Statements¶
- 0:00:00 "I'm showing a bug I found in the processing of auto renewals"
- 0:01:03 "It did get picked up. So the order did get picked up at 3am and started processing"
- 0:01:18 "It should have been updated to 2027 because at this point I've double purchased memberships, but also there's only one subscription and there's only one membership. So that didn't occur"
- 0:01:41 "Indeed the recurring order occurred last night at 3:01am and it went through. The transaction was approved. Braintree accepted it and processed it"
- 0:02:02 "For whatever reason, it got pushed back to this original order, which I wasn't expecting, and then also a new order wasn't created"
- 0:02:48 "The order product must have a price book entry that belongs to the price book related to the parent order price book entry ID" [ERROR MESSAGE]
- 0:03:00 "Something's happening where the price book is a mismatch"
- 0:03:23 "We need to understand how to resolve these things, how to identify them, and then how we resolve these items where people are being charged, but the entire process is not finishing"
- 0:03:39 "Do we manually add memberships? We need to talk about it" [ACTIONABLE]
Systems & Configurations¶
Systems Mentioned¶
- Salesforce (orders, subscriptions, flows)
- Chargent (recurring payments)
- Braintree (payment processing)
- Experience Cloud (join/renew process)
Test Setup¶
| Step | Action |
|---|---|
| 1 | Create new account |
| 2 | Join via Experience Cloud |
| 3 | Set up auto-renewal with NP membership |
| 4 | Modify transaction date to last year |
| 5 | Wait for 3am batch processing |
Error Details¶
| Field | Value |
|---|---|
| Time | 3:01 AM |
| Error Type | Flow failure |
| Error Message | Order product must have price book entry... |
| Transaction | Approved (Braintree) |
| New Order | Not created |
| Dues Paid Through | Not updated |
Expected vs Actual¶
| Item | Expected | Actual |
|---|---|---|
| New order | Created | Not created |
| Transaction | On new order | On original order |
| Dues paid through | 2027 | Unchanged |
| Subscriptions | 2 | 1 |
Credentials/Access Mentioned¶
- Salesforce admin for testing
- Email logs for error monitoring
Vendor Contacts Mentioned¶
- I2C (Salesforce implementation team - implied)
Errors & Troubleshooting¶
- Issue: Chargent order payment received flow failure
- Cause: Price book mismatch on order product
- Resolution: TBD - needs discussion
-
Timestamp: 0:02:35
-
Issue: Member charged but not renewed
- Cause: Flow failure after successful payment
- Resolution: May require manual membership addition [ACTIONABLE]
- Timestamp: 0:03:39
Transcript Gaps & Quality Notes¶
- Bug documentation recording (4 minutes)
- Critical issue for production launch
- Questions raised but not resolved:
- How to identify affected members
- How to manually resolve (add membership?)
- Price book configuration fix
- Possible solution mentioned: "charge and order price book"