Diya fix (orgSummaryEmail): Fixed Total Org Weekly Summary Email Flow#2090
Merged
one-community merged 2 commits intodevelopmentfrom Mar 7, 2026
Merged
Conversation
This was referenced Mar 6, 2026
one-community
approved these changes
Mar 7, 2026
|
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
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.


Description
Related PRS (if any):
This is an update on the old PR #1291
This backend PR is related to the frontend PR #4953
Main changes explained:
How to test:
npm install,npm run build,npm run devnpm run build, ensure you update your .env file with Gmail client ID, secret ID, refresh token, and puppeteer variablesScreenshots or videos of changes:
OrgWeeklySummary.mp4
Note:
Ensure both frontend and backend are running. Add logs if required, it takes a while for the email to go through!