Who can use this
- Desktop users recovering from a missed recording or failed upload.
- Admins and operators collecting details before escalating.
Before you start
- Keep the app open if an upload might still be in progress.
- Confirm the app is signed in as the same user as the dashboard.
- Note whether the recording was calendar-sourced, detected, Quick Note, or manual.
Steps
- Check whether the recording indicator ever became active.
- Confirm macOS permissions and quit and reopen the app if permissions changed.
- Check whether the meeting already has a cloud-bot recording.
- Look for processing or failed recording status in Ergo.
- Retry processing only when Ergo shows a retry path.
- If the meeting had no calendar invite or was never detected, use Quick Note or a manual note and add context for the team.
What to expect
- Missed detection can come from calendar visibility, meeting URL availability, disabled auto-record settings, or a runtime app issue.
- Calendar-less meetings may require a manual Quick Note start instead of auto-detection.
- Upload failures can come from network interruption, app shutdown, or missing upload data.
- Retry requires the backend to have enough upload and recording metadata.
- If a recording was skipped as a stub, it may not create a normal meeting record.
Common issues
- Auto-record detected meetings is off.
- The meeting was joined from a different account, alias, or calendar than the connected user.
- The app was closed before upload completed.
- The recording button does not respond until the app is fully quit and reopened.
- The recording is in failed status but missing data needed for retry.