## TL;DR
Link the recorder to the right calendar by matching the organizer address on the event with the connected Avoma account, add the recorder as a guest or enable recording for external organizer events, then use the record now option for the missed call series. Start with the Avoma recorder status for the discovery call, the calendar event it looked for, and the organizer match on that event, 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
Avoma recorder error "calendar event not found" discovery call never recorded
```

## Use this when
- You see this exact message or symptom: Avoma recorder error "calendar event not found" discovery call never recorded
- 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 Avoma recorder status for the discovery call, the calendar event it looked for, and the organizer match on that event, 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 organizer of the calendar event, which calendars Avoma watches, and the rule for events organized outside the team. 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: link the recorder to the right calendar by matching the organizer address on the event with the connected Avoma account, add the recorder as a guest or enable recording for external organizer events, then use the record now option for the missed call series. 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 a test event with the same organizer pattern shows the recorder scheduled before the start time
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
### Avoma recorder error "calendar event not found" discovery call never recorded
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: Avoma and the connected calendar at current versions

## Why it happens
Avoma schedules recording from calendar events it can see and match, so a call organized by a prospect or on an unconnected calendar produces a calendar event not found result and no bot joins.

## Provenance

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