FindingcurrentGTM data

A recurring meeting's join id names the series rather than a single meeting

Because a weekly call reuses one join id, every week's transcript lands on one meeting record.

SymptomOne meeting record holds transcripts from several different weeks, or a weekly series shows as a single meeting.

Keying meetings on the conferencing join id is the standard move because that id appears in both the invite and the recording.

In a recurring meeting, though, the join id belongs to the series. Zoom's support article on scheduling a recurring meeting says each occurrence of a recurring meeting uses the same meeting ID and settings. Because every occurrence reuses that id, a single weekly call's meeting record keyed on the join id alone can quietly collect every week's transcripts, leaving a summary of the meeting to read months of calls as one.

So identity is the join id plus the occurrence's scheduled start time, or the platform's occurrence id where it has one. Match each recording to the nearest scheduled occurrence, within half the series interval. A personal-room link is not a meeting id at all.

In a synthetic test set with one weekly series over 12 weeks, keying on the join id alone put all 12 transcripts on one meeting record; adding the scheduled start left one on each. The set shows the mechanism, not how common it is.

Check your setup read-only

Count recordings or transcripts per meeting record. List the records with more than 1. Match each recording's start time to the series' scheduled occurrences. Recordings from different occurrences under 1 record mean the id names a series.

Passes ifEvery meeting record with more than one recording or transcript has all of them matched to the same scheduled occurrence.

Access needed:call-data

If it fails: changes to make later (not part of the check)
  1. 01Key meeting identity on the join id plus the occurrence's scheduled start time, not the join id alone.
  2. 02Never key on a personal-room link alone. A personal-room link is not a meeting id.
  3. 03Prefer the platform's occurrence id when the platform has one. Otherwise, attach a recording to the nearest scheduled occurrence within half the series interval.
  4. 04Count records holding recordings from more than one occurrence as a standing check.
Applies ifYou back-fill call recordings or transcripts onto CRM or calendar meeting records by matching on join link or meeting id.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.