## TL;DR
Wait for the Gong call transcription status to reach complete and then re-run the summary against that call id, checking that the call id in the CRM link matches the recorded call, because the summarizer ran while the transcript did not exist yet (or against the wrong call) and an empty transcript can only produce an empty CRM note. Start with the Gong call record and its transcription status page, 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.

```text
Gong call summary error "transcript not found" CRM note empty failure
```

## Use this when
- You see this exact message or symptom: Gong call summary error "transcript not found" CRM note empty failure
- 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 Gong call record and its transcription status page, 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 Gong call id on the CRM record versus the call that was recorded, the transcription status and duration in Gong, and when the summary job ran relative to recording end. 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: Wait for the Gong call transcription status to reach complete and then re-run the summary against that call id, checking that the call id in the CRM link matches the recorded call, because the summarizer ran while the transcript did not exist yet (or against the wrong call) and an empty transcript can only produce an empty CRM note. 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 CRM note contains summary text sourced from the completed transcript
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
### Gong call summary error "transcript not found" CRM note empty failure
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: Gong call recordings with CRM note sync, webhook or automation triggered summaries.

## Why it happens
Transcription is asynchronous and takes minutes after a call ends. A summary job triggered on call end rather than on transcript ready reads nothing, succeeds quietly, and writes the empty result to the CRM.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_O-dP2AxnrzarlytkEiA9Nw