Investigation: Brighton Chapter Invitation Numbers (April 15-16, 2026) #2576
mroderick
started this conversation in
Maintenance
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
Investigated potential invitation issues for the Brighton chapter workshop scheduled for April 21, 2026. The data shows all eligible members were successfully invited on April 15, but there are significant findings about uninvited members from the pre-Terms of Service era and a duplicate batch attempt.
Brighton Chapter Timeline
Key Findings
1. Eligible Members Successfully Invited (April 15)
All members who accepted Terms of Service (TOC) were invited on April 15, 2026:
2. Members Not Invited - The TOC Gap
A significant number of registered members were not invited because they haven't accepted the Terms of Service:
Reason: These 653 members have
accepted_toc_at IS NULL3. Pre-2020 Members vs TOC Acceptance (The Root Cause)
The TOC requirement was introduced in February 2020. Members who registered before this date were not required to accept TOC during signup.
Students by Registration Year:
Coaches by Registration Year:
Key Insight:
4. Duplicate Batch Issue
A second invitation batch was triggered on April 16 for 594 students:
success_count: 593, failure_count: 1skipped_count: 0- no one was properly flagged as duplicate5. Dual-Role Members
34 Brighton members are registered as both students and coaches. These members appear in both invitation counts but represent unique individuals.
The Real Issue
This is not a technical bug with invitation delivery.
The 653 uninvited Brighton members represent legacy members who:
98% of these members registered before the TOC system existed.
Questions for Discussion
1. Outreach to Legacy Members
Should we proactively contact the 639 pre-2020 members who never accepted TOC? These are long-standing community members who may not realize they're excluded from invitations.
Suggested approach:
2. Historical Data Policy
Do we want to:
3. Duplicate Invitation Prevention
Should the invitation manager check for existing workshop invitations before creating new ones? The April 16 batch re-invited 594 already-invited students.
4. Visibility
Should chapter organisers have visibility into:
Data Sources
Analysis performed on production database snapshot:
Recommended Next Steps
Investigation conducted April 16, 2026
Beta Was this translation helpful? Give feedback.
All reactions