MediumDatabase
Callback not firing at scheduled time
Scheduled callback is set but never re-enters the hopper at the expected time.
Symptoms
- •Agent or customer expected callback at X time, call never made
- •vicidial_callbacks table shows the entry, still marked ACTIVE past the callback time
- •Hopper never pulls the callback lead
Common causes
- •Callback status (`status='ACTIVE'`) not being queried by hopper fill
- •Time zone mismatch between server and lead's expected callback time
- •Personal callback but the assigned agent isn't logged in at the callback time
- •Campaign rules excluding the callback state
How to fix it
- 1Verify callback is ACTIVE: `SELECT * FROM vicidial_callbacks WHERE lead_id=X`
- 2Check lead's current status, may have been updated by another process
- 3Review campaign's `dial_statuses` to ensure CALLBK is included
- 4Confirm server timezone and lead time-zone alignment
How VICIPanel helps
VICIPanel's callback dashboard shows all upcoming callbacks with firing-time countdown; overdue callbacks are flagged immediately so they can be manually triggered.
Related issues
More Database errors
Database connection lost
VICIdial cannot reach MySQL/MariaDB, everything stops.
Lead list not loading to hopper
Imported list exists but leads never appear in the hopper for dialing.
Report times out loading
Running a report (especially on large date ranges) times out before returning data.
Time synchronization error
Server clock drift is causing auth failures, SSL issues, or report inconsistencies.
Stop troubleshooting. Start operating.
VICIPanel's health dashboard catches most of these issues before they impact your agents — with plain-English diagnostics and one-click remediation.
