The calls logs are missing in the account. Can we please have these restored. See attached screenshot. ORG ID: ebf3317d-518e-46da-9e76-eaebb5aa5e4e CALL DATE RANGE: 16-18th of February Please note: We're doing more calls today and they are showing in this filter.

Thank you for reporting the missing call logs. To help us investigate, could you please specify the exact date range or any specific calls (with call IDs, if available) that are missing from your account? This will help us review your account and assist you more efficiently. If you have already checked the [dashboard call logs section](https://dashboard.vapi.ai/calls), please let us know what you observed. Sources: - [Vapi Issue Reporting Documentation](https://docs.vapi.ai/issue-reporting) - [Vapi Call Recording & Logging Documentation](https://docs.vapi.ai/assistants/call-recording) - [Vapi Debugging Documentation](https://docs.vapi.ai/debugging)

@Vapi done (updated description)

@Haii I have dealt with this exact issue a couple of times before missing call logs for a specific date range usually comes down to either a pipeline sync issue or a display/query filter bug rather than actual data loss, so the Feb 16–18 logs are most likely still intact. The key distinction is whether the data is missing at the ingestion layer or just failing to render on the dashboard both have different fixes but are very resolvable. Are the logs missing only on the dashboard, or are they also absent when pulled via API or export?

Thank for your help. Good news, the calls are there via API, but unfortunately can't export as there's nothing to export from the dashboard with those date filters. I've just tried filtering on those specific dates 16-18 and the logs are showing in dashboard. So, the issue appears to be with the date filtering being a broader range?

@Haii What you mean is that so the data is intact and the API confirms that, which is the best case scenario here. The fact that the logs show up when filtering the exact dates (16–18) but not on a broader range tells me this is almost certainly a date range query bug likely a boundary condition issue where the broader filter is either offsetting the timestamps or the query isn't inclusive of those dates when part of a wider range. When you apply the broader date range, does it completely skip the 16–18 logs or does it show partial records from those days?

If calls from Feb 16–18 are missing but newer calls are appearing correctly, this is likely a temporary logging/indexing issue rather than data loss. Sometimes logs don’t surface in the dashboard due to filter indexing or backend sync delays. check the log ingestion pipeline for your org (ebf3317d-518e-46da-9e76-eaebb5aa5e4e) and verify whether those records need reindexing. In the meantime, please confirm no additional filters (status, campaign, direction) are applied in the dashboard.

Hey Call logs can be deleted for the following reasons: 1. Manual Deletion (API/Dashboard) 2. Data Retention Policy (compliance plans like HIPAA and 14 days default for PAYG accounts) 3. Campaign Deletion: Calls belonging to deleted campaigns are marked call-deleted Please let me know if your issue still persists. Thank you