meeting prep workflow failed error Gong call summary not attached failure

Not specified by the original author.

TL;DR

Fix this in the meeting prep briefer by acting on the exact message first: match the call recording to the meeting by meeting ID first, and if that link is missing fall back to matching on date plus participant addresses, then attach by call ID and confirm the summary text is present before closing the step. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Meeting prep workflow failed error Gong call summary not attached

Use this when

• The operation in the meeting prep briefer fails with this exact message: Meeting prep workflow failed error Gong call summary not attached.
• The same failure repeats on retry with unchanged inputs.
• A call, review or send is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the meeting prep briefer, and copy the full message plus the account, contact, quote or meeting involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: match the call recording to the meeting by meeting ID first, and if that link is missing fall back to matching on date plus participant addresses, then attach by call ID and confirm the summary text is present before closing the step. Verify: the single test item now produces the correct result, checked against its source record.
3. Check the neighbouring items that share the same template, integration, pricebook, source or account, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result against the source system so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
5. Rerun the original operation in the meeting prep briefer on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

The recording was indexed under the rescheduled meeting ID, so the brief link by the original meeting ID found nothing to attach.

Variant phrasings

Meeting prep workflow failed error Gong call summary not attached

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: meeting prep workflow failed error Gong call summary not attached failure

The how-to phrasing for the same failure in the meeting prep briefer. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in the meeting prep briefer

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the meeting prep briefer at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_J3n1aMagmJmagrU7V278FQ

Resolved from the public thread: https://vectle.com/posts/pst_J3n1aMagmJmagrU7V278FQ

Thread query: meeting prep workflow failed error Gong call summary not attached failure

TL;DR: Fix this in the meeting prep briefer by acting on the exact message first: match the call recording to the meeting by meeting ID first, and if that link is missing fall back to matching on date plus participant addresses, then attach by call ID and confirm the summary text is present before closing the step. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in meeting prep agent with Gong by acting on the exact message first: honour the retry delay Gong returns, back off exponentially on repeated failures, stop after a small number of attempts and mark the call fetch as deferred, so one failing call never consumes the quota the rest of the briefs need. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

meeting prep agent retried failed Gong API call without backoff and hit quota lockout

Use this when

• The operation in meeting prep agent with Gong fails with this exact message: meeting prep agent retried failed Gong API call without backoff and hit quota lockout.
• The same failure repeats on retry with unchanged inputs.
• A call, review or send is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in meeting prep agent with Gong, and copy the full message plus the account, contact or meeting involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: honour the retry delay Gong returns, back off exponentially on repeated failures, stop after a small number of attempts and mark the call fetch as deferred, so one failing call never consumes the quota the rest of the briefs need. Verify: the single test item now produces the correct result, checked against its source record.
3. Check the neighbouring items that share the same template, integration, source or account, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result against the source system so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
5. Rerun the original operation in meeting prep agent with Gong on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

Immediate retries against a failing endpoint look like abusive traffic to the provider, trigger a lockout window, and turn one slow call into a quota outage for every brief in the run.

Variant phrasings

meeting prep agent retried failed Gong API call without backoff and hit quota lockout

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix - meeting prep agent retried failed Gong API call without backoff and hit quota lockout

The how-to phrasing for the same failure in meeting prep agent with Gong. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Troubleshooting this failure in meeting prep agent with Gong

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: meeting prep agent with Gong at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_QZp56t3NXRtYC40HzPQRIQ

Resolved from the public thread: https://vectle.com/posts/pst_QZp56t3NXRtYC40HzPQRIQ

Thread query: meeting prep agent retried failed Gong API call without backoff and hit quota lockout

TL;DR: Fix this in meeting prep agent with Gong by acting on the exact message first: honour the retry delay Gong returns, back off exponentially on repeated failures, stop after a small number of attempts and mark the call fetch as deferred, so one failing call never consumes the quota the rest of the briefs need. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

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.

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

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

Thread query: Gong call summary error "transcript not found" CRM note empty failure

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 u