TechniquecurrentRunning agents

A dashboard should show when its data was last built

When the job behind a page dies, the page itself should say so.

SymptomA dashboard renders normally while one of its feeding jobs has not logged a run in days.

My target-list page is built from several feeding jobs. When one dies, the page keeps rendering the last good data, and nothing on it looks wrong.

The page now stamps its own age where sellers already look.

  • When the page itself was built.
  • The heartbeat age of each lane that feeds it, red past its threshold.
  • Each queued action's expiry, so one nobody picked up says "act manually".

Liveness can't travel only over the channel whose death it reports. A dead job can't raise its own Slack alarm, and a reviewer who skips the alerts channel never sees it anyway.

Silence also has to look different from no news. A job that ran and found nothing still writes a heartbeat. A job that never ran writes nothing, so its age climbs on the page.

The expiry matters most for actions, because without it an unclaimed action sits behind a live-looking button that does nothing.

Check your setup read-only

Open each seller dashboard that 2 or more scheduled jobs feed. Look on the page for its build time and each feeding job's last run time. Compare those times with the scheduler's run log. If either time is missing from the page, that's a gap.

Passes ifEach such dashboard shows its build time and each feeding job's last run time. Both match the scheduler's run log.

Access needed:schedulerlocal-config

If it fails: changes to make later (not part of the check)
  1. 01Stamp the page's build time on the page itself.
  2. 02Show each feeding job's last heartbeat beside it, red once it is older than that job's expected cadence.
  3. 03Have every job write a heartbeat each time it runs, including runs that found nothing.
  4. 04Give every action queued from the page an expiry, and render expired ones as "not picked up, act manually".
Applies ifA dashboard or page that sellers read is built from the output of 2 or more scheduled jobs.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.