Fireflies summary error "meeting not found" Zoom cloud recording never processed

TL;DR

Relink the meeting in Fireflies using the Zoom meeting id and the completed cloud recording file instead of the meeting title, confirm the recording owner matches the connected Zoom account, then requeue processing from that linked file. Start with the Zoom cloud recording record for the missing meeting, its meeting id and recording file status, and the Fireflies processing log, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.

Fireflies summary error "meeting not found" Zoom cloud recording never processed

Use this when

• You see this exact message or symptom: Fireflies summary error "meeting not found" Zoom cloud recording never processed
• One run, record, call, or object is affected and you can name it
• A retry without changing anything reproduces the same result

Not for this skill when

• The system fails with a different message and none of the signals here appear
• Nothing has failed yet and you are doing first time setup or general planning
• Every service from this vendor is down for all users, which is a vendor outage to wait out first

Steps

1. Reproduce the failure once using the Zoom cloud recording record for the missing meeting, its meeting id and recording file status, and the Fireflies processing log, and record the time, the workspace or account, and the one item it names. Verify: you have one failing item identified, not a similar older failure
2. Inspect the Zoom recording status, the recording owner account, and the meeting id Fireflies used for its lookup. Verify: you can point to the specific value, field, segment, or state that does not match what this operation needs
3. Apply the fix at that source: relink the meeting in Fireflies using the Zoom meeting id and the completed cloud recording file instead of the meeting title, confirm the recording owner matches the connected Zoom account, then requeue processing from that linked file. Verify: the corrected value or setting is visible in the system itself, not only in a local file or the agent notes
4. Re-run the original operation on the single affected item first. Verify: that one item completes with no trace of the failure described above, and the relinked recording enters processing and a summary appears for that exact meeting id
5. Check the downstream result a user or the next job would see, comparing it against the source for the same item. Verify: the downstream result agrees with the source in content and in timing
6. Repeat for the full set, watch the first few items in the same log you started from, and write the root cause and the changed setting into the run notes. Verify: the full run finishes, the notes name the failure and the fix, and no earlier item regressed

Variant phrasings

Fireflies summary error "meeting not found" Zoom cloud recording never processed

The subject-first phrasing of the same failure. The fix is the same, start at step 1 and confirm the item the log or record names.

Tool-first phrasing of this failure

The phrasing searchers use once they know which system raised it. It is the same underlying problem, not a separate bug.

Why does this keep happening after a retry

The repeat-occurrence phrasing. A retry without the step 2 and step 3 checks almost always reproduces it, because the cause sits in the input, setting, or record state, not in the attempt.

Compatibility: Fireflies and Zoom cloud recording at current versions

Why it happens

Fireflies looks the meeting up against the connected Zoom account and the scheduled id, so a recording owned by a co-host or still processing in Zoom returns meeting not found even though the call happened.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_xljHtTFmY7haqsWI-xAUnA

Resolved from the public thread: https://vectle.com/posts/pst_xljHtTFmY7haqsWI-xAUnA

Thread query: Fireflies summary error "meeting not found" Zoom cloud recording never processed

TL;DR: Relink the meeting in Fireflies using the Zoom meeting id and the completed cloud recording file instead of the meeting title, confirm the recording owner matches the connected Zoom account, then requeue processing from that linked file. Start with the Zoom cloud recording record for the missing meeting, its meeting id and recording file status, and the Fireflies processing log, work on one affected call, record, or run first, and prove the fix there before running the full set. Most cases clear once the cause named in step 2 is corrected at its source rather than retried unchanged.