Use this checklist when you directly observed a visit but cannot find the corresponding event. If the only evidence is an empty app list, start with the no-visitors guide instead. Recording, notifications and identification are separate parts of the investigation.
Record the event and match the device
Write down the visit time, time zone, what you saw and how you observed it. Record the physical model/configuration, supplied guide edition, app and version, phone system and whether you are the owner or an invited user. Do not post passwords, pairing codes or full account details.
Choose the O-kam Pro reference, the VicoNature reference, or the other/unmatched-app route. These are guide-edition branches, not proof that every current batch uses one of those two apps.
Find the stage that is missing
| Stage | Evidence to keep | Avoid this shortcut |
|---|---|---|
| Device availability | Status shown, whether live view opens and when it was checked | A later live-view success does not establish availability at the earlier visit |
| Event creation | Exact event time, documented recording/detection mode and any prompt | Do not treat manual live recording as proof that automatic events were working |
| Storage and playback | Whether you checked card or cloud, the displayed date and whether the clip opens | One source's empty list is not evidence that all sources are empty |
| Notification | Whether the event exists and whether an alert arrived | No alert does not automatically mean no recording |
| Identification | Whether the video exists and whether identification is available | A missing or wrong bird name does not erase the visit |
Use the blank observation log rather than filling unknown fields with assumptions. Do not pay for a plan simply because an unrelated stage is uncertain; consult the service distinctions.
Check only controls documented for this combination
The app-specific references distinguish known guide statements from current steps still needing verification. Do not copy another app's menu path, a different model's restart duration or a sensitivity suggestion intended for empty triggers.
A supervised observation can help establish the current behavior after the correct instructions are confirmed. Record whether the app was in live view, when the visit happened and what appeared afterward. Do not assume watching live view leaves automatic detection unchanged: V9/V11 guide editions describe a relevant live-view limitation in their own references.
Do not stage contact with birds, format a card, delete events, remove the device or perform a factory reset as a generic first test. Preserve the available evidence.
Keep the result and ask a specific question
If the event remains missing, report the failed stage with the device/configuration, app version, account role, time zone and card/cloud source. Add the exact displayed message or a redacted screenshot. A useful question is whether that combination should have created an event under the conditions you recorded.
If the clip exists but the alert is missing, identify it as a notification issue. If only the identification is missing, identify it as an AI/identification issue. For keeping a playable copy, use saving and verification. Those tasks may need different evidence and permissions.