Skip to content

Zoom Recaps to Slack: only post recaps from the last 48 hours - #7

Closed
rrrutledge wants to merge 2 commits into
mainfrom
zoom-recaps-48h-cutoff
Closed

rrrutledge wants to merge 2 commits into
mainfrom
zoom-recaps-48h-cutoff

Conversation

@rrrutledge

Copy link
Copy Markdown
Contributor

Zoom Recaps to Slack has been posting one old recap almost every day since 10-29 (Summit Planning from 10-19, Board from 04-23 and 08-27, and so on), which Addie noticed on 11-05.

Zoom's summaries list ignores the date window and returns about 994 summaries back to June 2024.
Build Candidates picked the newest unposted occurrence from any date, so any run with nothing new dug into history.
A webhook whose own meeting the 8:00 AM sweep had already posted fell back to the series' newest unposted occurrence.

Now a meeting that started more than 48 hours ago is never a candidate, for both the sweep and the webhook.
A webhook run considers only the exact occurrence that fired it; if that one is already posted or not ready, the run ends with nothing.

Review findings rejected:

  • A webhook that fires before its summary is listed or ready now posts nothing instead of falling back to another occurrence; the next 8:00 AM sweep posts it while it is still inside the 48 hours, and the fallback is what produced the old recaps.
  • The cutoff keys on meeting start, not summary readiness; a recap Zoom takes more than 48 hours to produce is dropped, which is the intended trade.
  • A summary with no parseable start time is dropped; that is the right outcome.
  • Fetching with a real date window instead of a cutoff is out of scope here; Zoom ignores the window, which is why the cutoff exists.

The 1-hour wait before posting is already in main (#3), so no other change is needed here.

🤖 Generated with Claude Code

rrrutledge and others added 2 commits November 7, 2026 06:54
…k handles only its own meeting

Zoom's summaries list ignores the date window and returns meetings back to 2024, so a run with nothing new dug into history and posted old recaps almost daily.
Now a meeting that started more than 48 hours ago is never a candidate, and a webhook run considers only the exact occurrence that fired it, with no fallback to another occurrence of the series.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AEavKGR3wFFUQXR9W16mSQ
…ff, rewrap header

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AEavKGR3wFFUQXR9W16mSQ
@rrrutledge
rrrutledge marked this pull request as ready for review November 7, 2026 21:34
@rrrutledge

Copy link
Copy Markdown
Contributor Author

Superseded by #8, which fixes the same old-recap bug on main.

@rrrutledge rrrutledge closed this Nov 7, 2026
@rrrutledge
rrrutledge deleted the zoom-recaps-48h-cutoff branch November 7, 2026 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant