VICIdial Error: Callback Not Firing — Cause & Fix

Error Summary

Error Message

Callback Not Firing

Severity

Warning

Component

Web

What Causes This Error

Scheduled callbacks are not being dialed at their configured times. Causes include: VICIdial cron job (vicidial_callback_check.pl) is not running, scheduled_callbacks is set to N in campaign, the CALLBK status is not in dial_status_filter, callback lead recycling is not configured, or the server time is wrong causing time comparison failures.

How to Fix It

  1. 1
    Verify callback cron is running: crontab -l -u root | grep callback
  2. 2
    Check cron execution: tail -50 /var/log/cron
  3. 3
    Verify campaign has scheduled_callbacks = Y in Admin > Campaigns
  4. 4
    Ensure CALLBK is in dial_status_filter
  5. 5
    Check callback queue: SELECT * FROM vicidial_callbacks WHERE callback_time < NOW() AND status='ACTIVE'
  6. 6
    Verify server time is correct: date
  7. 7
    Manually trigger callback check: /usr/share/astguiclient/vicidial_callback_check.pl

How to Prevent It

Monitor cron job execution regularly. Include CALLBK in all campaign dial_status_filter templates. Test callback scheduling during initial campaign setup. Document callback configuration in campaign setup documentation.

Warning Time Synchronization Error Web Critical Hopper Empty Web Critical List Not Loading Web

Still Stuck?

ViciStack's free 30-day support plan includes unlimited live VICIdial troubleshooting. If you can't resolve this error with the steps above, our engineers will connect to your system and fix it directly — no support tickets, no hourly billing.

Get Free VICIdial Support →

Frequently Asked Questions

What causes the VICIdial "Callback Not Firing" error?
Scheduled callbacks are not being dialed at their configured times. Causes include: VICIdial cron job (vicidial_callback_check.pl) is not running, scheduled_callbacks is set to N in campaign, the CALLBK status is not in dial_status_filter, callback lead recycling is not configured, or the server time is wrong causing time comparison failures.
How do I fix the VICIdial "Callback Not Firing" error?
Verify callback cron is running: crontab -l -u root | grep callback Then: Check cron execution: tail -50 /var/log/cron Then: Verify campaign has scheduled_callbacks = Y in Admin > Campaigns Then: Ensure CALLBK is in dial_status_filter Then: Check callback queue: SELECT * FROM vicidial_callbacks WHERE callback_time < NOW() AND status='ACTIVE' Then: Verify server time is correct: date Then: Manually trigger callback check: /usr/share/astguiclient/vicidial_callback_check.pl
How can I prevent the "Callback Not Firing" error in VICIdial?
Monitor cron job execution regularly. Include CALLBK in all campaign dial_status_filter templates. Test callback scheduling during initial campaign setup. Document callback configuration in campaign setup documentation.