# Eleven Weeks of Green Runs and an Empty Article Queue

> A content dispatcher ran green every morning for eleven weeks and published nothing, because the queue had been empty since 5 August and no automated refill existed.

- Author: Dil Ahdan (https://dil.dev/)
- Published: 2026-11-09
- Updated: 2026-11-09
- Tags: content-pipeline, automation, agents, local-seo
- Canonical: https://dil.dev/notes/empty-queue-green-runs-no-articles/

## Key takeaways

- A dispatcher run that finishes in under one second dispatched nothing: that is the signal to watch.
- The queue sat at zero from 5 August because the weekly refill skill was last run by hand on 20 July and was never automated.
- Monday-only runway emails meant three weeks of warnings arrived before anyone acted.
- The fix was a manual refill on 23 October and a weekly shortlist routine that requires human approval before rows enter the queue.
- Green CI is not proof of output: you need a separate check on what the job actually did.

The Drainiacs content pipeline ran its 07:00 dispatcher every single day from early August through to late October 2026. Every run exited cleanly. Nothing published. The queue had been empty since 5 August and nobody had set up an automated way to refill it.

## What the Pipeline Actually Does

The dispatcher picks up rows marked Queued and turns them into published articles. It runs at 07:00 daily and takes two rows per day when they exist.

- **Queue source:** briefs written by a refill skill, appended as rows into a shared queue.
- **Publish cadence:** two rows consumed per day at 07:00.
- **Refill step:** a separate skill, run by hand, not on a schedule.

The refill skill was last run manually on 20 July 2026. After that, the queue drained naturally. The last row cleared on 5 August.

## The Signal Everyone Missed

A dispatcher run that finishes in under one second dispatched nothing. That is documented behaviour in the AGENTS.md for this project. The job does not error. It does not warn loudly. It just finds zero rows, exits cleanly, and the run log looks identical to a successful publish.

Exit-code monitoring is useless here. You need to track rows dispatched per run. A zero on a day when the queue should have content is the alert that matters.

Eleven weeks of sub-second runs sat in the logs. All green.

## Why the Audit Warnings Did Not Help in Time

There was a daily audit running at 10:00. It did detect the empty queue and it did emit a `QUEUE RUNWAY LOW: 0 Queued` warning. The problem is that runway findings only email on Mondays, a change made on 30 September.

That means the warnings landed on:

- Monday 5 October
- Monday 12 October
- Monday 19 October

Three separate Monday emails, each saying the queue was empty. By the time the third one arrived, the queue had been dry for eleven weeks. Weekly emails are easy to skim past, especially when the rest of the pipeline looks healthy.

Daily audit, weekly signal. The mismatch is the gap.

## The Refill That Should Have Been Automatic

The weekly refill routine was meant to call the refill skill on a schedule. It was never armed. The docs describe it as a routine, but no scheduler ever pointed at it.

This is a common failure mode with manual-first workflows. You build the skill, you document the routine, you run it once to prove it works, and then you move on. The automation step feels like a detail. It is not.

The refill skill itself works fine. On 23 October, Dil ran it by hand and the Queue Appender wrote 11 deduplicated gap briefs as rows 87 to 97. The pipeline started publishing again the next morning.

The skill was never the problem. The missing scheduler call was.

## What the Fix Looks Like

The fix has two parts.

**Manual refill on 23 October.** Eleven gap briefs queued as rows 87 to 97. Pipeline resumed. Immediate problem solved.

**A weekly shortlist routine with human approval.** Rather than fully automating the refill, the new routine emails a shortlist of candidate briefs once a week. A human approves before anything enters the queue. The Queue Appender only runs after that approval.

This is a deliberate choice. Full automation would risk queuing briefs that are subtly off-brief or duplicated in ways the deduplication step does not catch. The approval step is cheap and it keeps the content quality check in the loop.

The weekly routine also needs to actually be armed this time. That is the lesson.

## Runway Maths Worth Knowing

At two rows per day, eleven briefs buys roughly five and a half weeks of runway. That is not a lot of buffer.

- **Minimum sensible refill interval:** monthly, assuming you want at least two weeks of headroom.
- **Comfortable buffer:** twenty to thirty rows, which is ten to fifteen weeks at this cadence.
- **Warning threshold:** email daily, not weekly, when queued rows drop below a week's worth.

The Monday-only email rule made sense as a noise reduction measure. It needs an exception for zero-runway states.

## What I'd do differently

- **Arm the scheduler before closing the task.** The refill routine was documented and tested. The missing step was pointing a scheduler at it. That should be a checklist item, not an afterthought.
- **Alert daily on zero-runway, not weekly.** The Monday cadence is fine for low-runway warnings. Zero rows is a different severity. It should email the same day it hits zero.
- **Log rows dispatched, not just exit code.** A sub-second run with zero dispatches should appear in a dashboard somewhere visible, not just in raw logs. If I'd had a simple "articles published today: 0" metric surfaced anywhere, this would have been caught in week one.
- **Set a calendar reminder for the first refill after any manual run.** Until the scheduler is proven reliable, a recurring calendar event is a reasonable backup. Boring, but it works.

## Quick answers

**How do I know if my content dispatcher actually published anything?**

Check the run duration. A dispatcher that processes real rows takes measurably longer than one that finds nothing to do. A run finishing in under one second is a reliable sign it dispatched nothing, regardless of the exit code.

**Why did the queue run dry without anyone noticing for eleven weeks?**

The refill step was a manual skill, last run on 20 July. No automated routine called it again. The daily audit did flag a zero-runway warning, but those emails only fired on Mondays, so the signal arrived weekly rather than daily and was easy to miss.

**What is a queue appender in this context?**

It is the step that writes new brief rows into the content queue. In this pipeline, 11 deduplicated gap briefs were added as rows 87 to 97 during the manual refill on 23 October.

**Should I fully automate the refill or keep a human in the loop?**

Dil kept a human in the loop deliberately. The weekly routine emails a shortlist of candidate briefs for approval before anything enters the queue. Full automation risks publishing briefs that are off-brief or duplicated in ways deduplication misses.

**How often should a content dispatcher run to stay healthy?**

That depends on your queue depth and publish cadence. This pipeline consumed two queued rows per day at 07:00. At that rate a queue of eleven briefs buys roughly five weeks of runway, so a monthly refill check is the minimum sensible interval.

**What is the right monitoring signal for a pipeline like this?**

Track rows dispatched per run, not just exit code. A zero-dispatch run on a day when the queue should have content is an actionable alert. Exit-code-only monitoring will stay green while the pipeline starves.
