A healthy application does not prove its periodic detector is running

When a workflow is past a code-defined threshold but no operational record appears, verify the detector's scheduler as a separate deployed component before debugging eligibility logic. A web application can remain healthy while a cron, worker, or trigger service is absent or unscheduled.

First prove that the persisted workflow meets the detector's exact status, recency, and required-step conditions. Then verify the live effective schedule, invocation logs, and durable detector output. Scheduler absence explains missed periodic detection only after those eligibility checks; it does not explain explicit in-app requests or event-driven paths.

Applicability: cron-driven support, reconciliation, and alert pipelines.