Hi Kyle,
I assume you are running Chrome connector on Windows machine, correct? To check if the problem is with delivering notifications or somewhere else could you please try following on the machine running Chrome connector:
- Close all Chrome windows.
- Open "Task Manager", click Processes tab, add Command Line column (menu View -> Select Columns... -> select Command Line down in the list -> click OK)
- See if you still have Chrome process running. If you do make sure command line contains "--type=service" string. (if you don't have Chrome process with "--type=service" that is the problem)
- Select Chrome process with "--type=service" in command line and click "End Process" button.
- Now you should have no Chrome processes running.
- Start Chrome browser now.
- Make sure Chrome process with "--type=service" also got started. (If it does not, go to Chrome menu -> Settings -> Advanced Settings check that Cloud Print is enabled. If so, "--type=service" should start now.) If for some reasons process did not start or cloud print is disabled in settings, let me know.
- Now, a Chrome process "--type=service" should poll all queued jobs and start printing them. If it does not - let me know, may be you have orphan/duplicate printers issue. If it does, wait until it printed the last job and try sending a new job to one of your printers. If it printed all old jobs, but failed to print new ones, it is likely and issue delivering print jobs notifications.
Could you please try steps above and let me know results.
Thanks,
Gene