Internal Cron
Shortlist Urgency Tick
Two TRUE urgency signals the system already knew (Epic 5.5).
- Availability change. An engineer on a live, already-viewed shortlist moved from an available state to a departed one. The comparison is against the status SNAPSHOTTED when the card was published, so the email is about an observed transition, never about a state we merely noticed for the first time.
- Expiry renewal. A parent token dies within three days. Day 11 of 14: trivially true, and the buyer can verify it on day 15.
The wave doc bans fabricated scarcity. Nothing here counts down, invents viewers, or names a competing offer. If neither condition holds, the tick sends nothing, which is the common case.
Idempotent: both notices stamp their dedupe column BEFORE the send, so a Resend outage costs one email instead of causing a re-send storm.
External GitHub Actions cron (shortlist-lifecycle-cron.yml), NOT in-process APScheduler — interval jobs starve on ephemeral Railway replicas (enrollment incident 2026-08-18).
post/api/internal/cron/shortlist-urgency-tick
Request
- Base URL: https://api.ruzora.com (the document declares no server; this is the origin it was published from)
- URL: https://api.ruzora.com/api/internal/cron/shortlist-urgency-tick
- Auth: none declared
Headers
x-cron-tokenstring nullable
Response
Successful Response
unknown required
Changes
No recorded changes to this operation across all 1 revision of this API.