The pattern is familiar. A parent signs up for summer camp in March without a hitch. In May they come back to add a second session, or register a sibling, and the Altru web form throws an error. A brand-new visitor fills in the same form a minute later and gets through fine. Since the form works for everyone else, the problem is almost never the form. It’s what Altru finds when it tries to match the returning person to a constituent record it already has.
Below is how we’d troubleshoot it, starting with the most common causes.
What changes the second time someone registers
A first-time registrant is easy for Altru. Nothing matches, so it creates a new constituent and attaches the registration. A returning registrant forces a decision. Altru has to work out which existing record this person is and whether the new registration conflicts with anything already on that record. Errors on repeat registrations usually come from one of these:
- Duplicate constituent records. If the same person exists twice (say, one record from a desk sale and one from an earlier web registration), the match can be ambiguous. Depending on your duplicate-matching settings, the transaction may fail or get attached to the wrong record.
- A shared email address. Families often register with one parent’s email, and that address may sit on several records: both parents, a household, sometimes a grandparent who bought a membership. A match on email alone can turn up more than one candidate.
- Conflicts with the existing registration. If the person, or the registrant they’re entering, is already registered for that event or program, a second registration may be blocked or may hit a per-person limit. Whether that shows a friendly message or a generic error depends on how the event is set up.
- Changed details. A new last name, a new address, or a typo in the first registration can produce a partial match on one field and a mismatch on another.
- Inactive, deceased, or merged records. If the record the form matches to has been marked inactive or merged into another, the registration can fail to post.
We aren’t certain how every Altru version reports each of these cases on the web, and the messages people see are often generic. Treat the list as places to look, not a confirmed diagnosis.
Diagnosing a specific failure
- Collect the details while they’re fresh. Get the registrant’s name, the email they typed, the event or program, roughly when it happened, and a screenshot of the error if possible. “It didn’t work” won’t get you far.
- Search constituents by that email. If it comes back with two or more records, you’ve very likely found the cause. Also search by name and address. Duplicates don’t always share an email.
- Open the record that holds the first registration. Check whether the person or their attendee is already registered for the event they were trying to book, and whether the record is active.
- Reproduce it in a sandbox if you have one. Register a test constituent once, then register again with the same email and slightly different details. Change one thing at a time (name spelling, email, attendee) until you can make the error happen on demand.
- Bring it to Blackbaud support with evidence. If you can reproduce it, send support the steps, the form name, and the constituent IDs involved. They can see server-side details that don’t show up in the browser.
Fixes that stop it from coming back
Clean up the duplicates you find
Merging the duplicate records usually fixes that person right away. Don’t stop there. Run a query for email addresses that appear on more than one constituent and work through the list before your next big registration window opens. Camp, class, and holiday-event seasons are when this shows up most, because that’s when the same families come back.
Revisit your duplicate-matching settings
Look at how strict your web transaction matching is. Settings that are too loose can attach a registration to the wrong person, and settings that are too strict can create a new duplicate every time. Neither is ideal, but if you change them, test both directions in a sandbox before production.
Make the event rules visible
If a family can’t register the same child twice, or there’s a per-person cap, say so on the registration page. A clear line of text beats a cryptic error, and it cuts down on support calls.
Give staff a workaround
Until the root cause is fixed, the front desk or registration team should know how to finish the registration by hand: find the correct record, add the registration, take payment, and note what happened. Families shouldn’t have to try the website three times.
Quick answers
Why does it fail for one family and not another?
Because the error depends on what already exists for that person in Altru. Families with duplicate records, shared emails, or an earlier registration for the same event are the ones who hit it.
Will merging the duplicate records fix past failed registrations?
No. A failed transaction generally didn’t post, so nothing is waiting to be recovered. Merge the records, then enter the missing registration or ask the family to try again.
Where Social Good fits
Data cleanup is the long-term fix whatever form you use. Some organizations also replace the Altru web forms they’re fighting with Checkouts, a branded, mobile-friendly checkout for tickets, memberships, and donations that writes its data back to Altru. If repeat-registration errors are one of several problems with your current forms, it’s worth comparing.
