Queue Monitor
The Queue Monitor (System → Queue) shows whether Threadline's background work is keeping up, and lets you fix jobs that failed.
What a queue is
When a customer sends a message, Threadline does not make them wait while it thinks. It puts the work (writing the reply, sending an email, processing a document, sending a campaign) on a queue, and a worker picks the jobs up one by one. On shared hosting the worker is started by your cron job.
The problem it solves
If the worker stops, nothing visibly breaks. Messages arrive but replies never go out, and documents sit on "Processing". This page makes that visible, and gives you a button to retry anything that failed.
What you see
- Waiting jobs, with a count per queue. This works with the database queue (shared hosting) and with Redis (VPS mode).
- Worker — Running when a worker has checked in during the last two minutes. A worker checks in every half minute while it waits, so this shows within half a minute of starting, even before it has any work. Last seen with a time means it has stopped checking in; Not seen yet means no worker has started since the install or the last update. Under it, Last job says when a worker last finished a job.
- A warning when the oldest waiting job is more than 10 minutes old. This almost always means the worker or the cron has stopped. See Cron Setup.
- Counts of automation runs and campaigns by status, next to it.
If Redis cannot be reached, Waiting shows a dash and a note says the jobs cannot be counted.
Failed jobs
When a job fails (for example a mail server was down), it is saved here instead of disappearing. Each row shows the job, the queue, the time and the first line of the error.
| Action | What it does |
|---|---|
| Details | Shows the full error trace, useful when asking for help. |
| Retry | Puts that job back on the queue. |
| Delete | Removes that one failed job. |
| Retry all | Puts every failed job back on the queue. |
| Delete every failed job | Removes all of them. You must type FLUSH first, so it cannot happen by accident. |
Retry after you fix the cause. If you retry while the cause is still there, the job simply fails again.
Common questions
"Waiting" keeps growing. The worker is not running. Check the cron on Cron & Health.
The same job keeps failing. Open Details and read the first line of the error. It usually names the problem (a wrong key, a full disk, a service that is down).
Only staff with Watch and retry background jobs can open this page.