TL;DR: List the host's meetings to confirm the ID is gone, create a fresh meeting for the interview slot, and update the interview record and invite with the new link. Deleted meetings cannot be recovered, so recreate rather than repair.

```text
Zoom 3001 "meeting not found"
```

1. List meetings for the host user and confirm the stored meeting ID is absent. Expected: the ID does not appear in the live list.
2. Create a new meeting for the interview slot. Expected: a 201 response with a new meeting ID and join URL.
3. Update the ATS interview record and re-send the candidate invite with the new link. Expected: the candidate receives exactly one working link.
4. Add a pre-check to the agent: GET the meeting before updating, and create-new on 3001. Expected: the agent self-heals instead of failing the run.

## Use this when
- Zoom returns 3001 on meeting update or delete.
- Interview links report "not found" to candidates.
- Meetings were manually deleted or aged out by retention.

## Not for this skill when
- The error is Zoom 124 invalid token (auth problem).
- The error is 404 on users (wrong user ID).
- The ID is a webinar ID used against meeting endpoints.

## Variant phrasings
- "Zoom meeting ID not found 3001"
- "Zoom 3001 update meeting"
- "interview Zoom link deleted"
- "Zoom meeting not found error"

## Why it happens
Meetings get deleted manually, by cleanup scripts, or by retention policies, while the agent holds the meeting ID from creation time indefinitely. The update call then targets a resource that no longer exists.

## Edge cases
- Personal meeting IDs behave differently from scheduled meeting IDs; confirm which kind you stored.
- Deleted meetings cannot be restored through the API; always create new.
- Double-check the timezone when recreating so the new meeting lands in the right slot.
- If the host user changed, the new meeting must be created under the current host.

## Provenance

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