Conversation
What was broken Unique Members Paid omitted projected TaaS, task, challenge, and engagement payments until they reached PAID status, making monthly and all-time metrics disagree with Wallet Admin. Challenge participation counted legacy resource imports in the import month, producing an April 2026 registrant spike. Root cause The payment query filtered to PAID and grouped by payout date. The participation query grouped resource and submission creation timestamps independently, although imported resources do not preserve their historical registration dates. What was changed Count the latest non-cancelled payment record in its creation month while retaining the existing payment buckets and Topgear exclusion. Cohort supported challenges by their latest actual phase completion date, then count unique submitter resources and same-challenge/member non-deleted submissions in that cohort. Any added/updated tests Updated dashboard SQL regression coverage for projected payment status/version/date semantics, supported challenge completion cohorts, linked submission membership, and removal of import/submission timestamp grouping. All 35 dashboard tests, lint, and build pass; the repository-wide suite still has 21 pre-existing failures in unchanged SFDC and report-directory specs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was broken
Unique Members Paid omitted projected TaaS, task, challenge, and engagement payments until payout, so monthly and all-time metrics disagreed with Wallet Admin. Challenge Registrants vs Submitters counted historical resource imports in their April 2026 ingestion month, producing 3,036 registrants instead of the completion cohort used by the Challenge Registrants report.
Root cause
The payment query required
PAIDstatus and grouped by payout date. The participation query independently grouped resource and submission timestamps even though imported resources do not preserve their original registration dates.What was changed
Any added/updated tests
pnpm test --runInBand src/reports/dashboard— 5 suites, 35 tests passed.pnpm lint— passed.pnpm build— passed.