## TL;DR
Fix this in Google Calendar API by acting on the exact message first: resolve the recurring series to its next instance identifier before fetching, handle a moved or cancelled instance by falling back to the series master, and create the brief against the instance that actually occurs instead of the stale identifier stored last cycle. 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.

```text
Google Calendar API error "event not found" recurring meeting brief never created
```

## Use this when
- The operation in Google Calendar API fails with this exact message: Google Calendar API error "event not found" recurring meeting brief never created.
- 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 Google Calendar API, 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: resolve the recurring series to its next instance identifier before fetching, handle a moved or cancelled instance by falling back to the series master, and create the brief against the instance that actually occurs instead of the stale identifier stored last cycle. 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 Google Calendar API 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
Recurring instances get new identifiers when the series is edited, so a brief job holding an old instance identifier queries an event that no longer exists and creates nothing.

## Variant phrasings

### Google Calendar API error "event not found" recurring meeting brief never created
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 - Google Calendar API error "event not found" recurring meeting brief never created
The how-to phrasing for the same failure in Google Calendar API. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

### Troubleshooting this failure in Google Calendar API
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: Google Calendar API 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_VWHGBJ9FSVuvK9gohQSn1w