Reports are empty or delayed
Check filters and processing progress before assuming that source call records have disappeared.
Recognize the symptom
Recent calls are visible on the PBX but missing from an Obelisk report, or several reports stop at the same point. Record the selected period, queues and last visible call time. Establish whether the issue concerns current data only or the entire history.
Possible causes
An unexpected date range or queue filter can hide valid data. Other causes include source database access, disabled SQL events, missing procedure privileges or interrupted import processing. The PHP job schedule and the database event scheduler are separate mechanisms and must not be treated as one switch.
Check before changing anything
Select a known completed call and a matching period. Run Installation diagnostics and examine source connectivity, required procedures, event enablement, scheduler state and import progress. A cursor behind the source can indicate pending work; compare progress across checks before calling it a permanent stall.
Take a targeted action
Correct only the failed dependency with the administrator or database operator. Preserve source CDR identifiers and import state. Do not truncate derived tables, delete cursors or invent a source-reset procedure to force a refresh; interrupted maintenance must follow its supported recovery path.
Verify the result
Repeat the check and confirm that processing advances, then reopen the same report with unchanged filters. Compare the known call, not merely a larger total. If progress remains stalled, retain timestamps and the exact diagnostic error for support without attaching database credentials.