All posts
Technical Implementation

Last-published-at beats scheduler flags for content systems

A green enabled flag can hide a starved SEO factory. Publish lag is the metric that catches uniqueness gates and silent pipelines. Free WCAG brief still starts at free-audit.

AE
AccessioAI Editorial
1 minute read

I spent months trusting a green flag.

content.scheduler.enabled was true. The LLM host was healthy. The job still “ran.” Last bulk English posts were stuck months earlier.

The boolean never flipped false. Publish lag did the work the flag refused to do.

What broke

After the catalog grew past several thousand titles, a title-similarity gate (Jaccard on word sets) started rejecting almost every new LLM title as “too similar.” Batch code looked busy. Scheduler looked enabled. Almost nothing new landed as a public post.

That is a classic silent failure: health checks that ask “is the switch on?” instead of “did anything ship?”

What I watch now

  1. last-published-at for the locale and channel you care about (for us, EN ecommerce / compliance content first)
  2. Success vs skipped counts per batch (duplicate title, model timeout, validation)
  3. Queue lag if generation is async — accepted jobs that never increase article counts are failed jobs

Configuration flags stay useful for kill switches. They are not proof of output.

What we changed in the factory

  • Raised the title-similarity threshold so new commercial angles can land without free-for-all spam
  • Added title templates tied to product wedges (free WCAG exposure brief, continuous monitoring, AI Act disclosure)
  • Made manual generate return quickly and run in the background so reverse proxies do not kill long LLM batches

If you run any content agent or SEO factory, instrument publish lag before you celebrate uptime.

Free storefront check (product, not a certificate)

If the reason you care about this pipeline is ecommerce compliance traffic, start with a free automated WCAG 2.2 exposure brief on a public URL:

Start free WCAG 2.2 audit →

It is not a VPAT and not legal advice. It is a source-level PDF of what automated checks find before you buy an overlay story.

Continuous monitoring and remediation queues:

Bottom line

If your dashboard only shows “enabled,” you can celebrate a machine that stopped shipping. Prefer last-published-at and real success counts. Flags hide starvation; lag surfaces it.