Repository navigation
Zoom Recaps to Slack: post only occurrences newer than the series' latest post - #8
Merged
Merged
Conversation
…ones Zoom's summary list ignores its from/to window and returns every summary back to 2024, and the Posted table only starts in August 2026, so the daily sweep was posting the newest never-posted occurrence each morning and walking back through history one old recap a day. A webhook run now considers only occurrences that started in the last 24 hours, and the sweep only the last 72 hours. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AEavKFor7ShF9r4gDJ6fY1
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AEavKFor7ShF9r4gDJ6fY1
Replaces the 24h/72h age cutoff: an earlier occurrence that never posted stays unposted once a later one in its series has, and a late-arriving recent occurrence still posts however long it took. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AEavKFor7ShF9r4gDJ6fY1
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AEavKFor7ShF9r4gDJ6fY1
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.
What was wrong
The bot has been posting months-old meeting recaps alongside the current ones.
In #summit2026planning it posted the Oct 19 meeting on Oct 31, Aug 27 on Nov 5, Jul 30 on Nov 6, and Jul 23 on Nov 7.
Most of these went out at 8:00 AM Central, when the daily sweep runs.
Those four posts and their "Full notes" replies have since been deleted.
Zoom's summary list ignores the workflow's
from/towindow.Today's sweep asked for Nov 4 to Nov 7 and got 994 summaries going back to June 2024.
The Posted table only starts in August 2026, so every older occurrence of a configured meeting looked unposted.
Each run then posted the newest of them, one step further back each morning.
The likely trigger is the earlier change that skips occurrences with nothing to post: before it, an empty occurrence at the front of the list ended the run before it reached the older ones.
What changes
Within each meeting series, an occurrence posts only if it started after the newest occurrence of that series already posted.
Once a later meeting has posted, an earlier one that never did stays unposted.
A series with nothing posted yet, such as one just added to Config, posts its newest ready occurrence.
The node doc states the rule and the reason for it.
Run against this morning's sweep data, the rule leaves 1 of the 165 old, unposted, configured occurrences eligible.
That one is an Oct 7 "ISC Board Meeting (Americas & Europe)" occurrence whose series has never posted, and the sweep has passed over it every day so far.
Until this merges, each morning's sweep posts the next older Summit Planning recap.
Review findings not taken
Zoom gives every summary in the list a start time, and the code before this change didn't guard against it either.
from/toquery on List Summaries stays as it is.Removing it changes nothing Zoom returns, and the doc now says Zoom ignores it.
🤖 Generated with Claude Code
https://claude.ai/code/session_01AEavKFor7ShF9r4gDJ6fY1