Apify Store Pulse pipeline status

A live health check for the daily census that powers Apify Store Pulse. If you're a reader: the badge below tells you whether today's data is current. If you're an operator or want to verify reproducibility: the technical pipeline details are further down.

FRESH
Data last refreshed 4 hours ago (2026-05-19 06:06 UTC)
The daily census ran on schedule. Numbers on Apify Store Pulse reflect the latest available Store data.

What's in today's snapshot

Latest valid baseline2026-05-19
Earliest valid baseline2026-03-29
Total valid baselines47
Continuous streak ending now40 days
7-day comparison point2026-05-12
Actors tracked25,903
Creators tracked3,027
Detail pages generated3422 actors · 245 creators
Lookup coverage25904 actors · 3026 creators

What's available to show today

Some views need more historical depth before they can show meaningful signal. Each one activates automatically once enough stable history accumulates.

1-day mover✓ enough history
7-day mover✓ enough history
30-day mover✓ enough history
3-week abandonment detector✓ enough history
Technical pipeline details (for operators and reproducers)

Pipeline diagram

06:00 UTC  → Apify Schedule fires
              apify-store-pulse-daily

06:00–06:05 → Actor runs (~5 min)
              apify-store-pulse — run history
              ↓
              Reads tracker.db from KV → fetch + ingest → compute pulse
              ↓
              Writes pulse_latest_* to KV
              apify-store-pulse-tracker (KV store)

06:30 UTC  → GitHub Action fires
              pulse-sync.yml
              ↓
              GET pulse_latest_* from KV → write to public/data/pulse/
              ↓ commit + push if changed

06:32 UTC  → Cloudflare Pages auto-deploy
              deploy.yml

06:35 UTC  → /pulse/apify + detail pages live with fresh data

Debugging when data is stale

  1. Check Apify run history — console.apify.com. Did today's scheduled run fire? Did it succeed?
  2. If Apify ran but data is old — check pulse-sync workflow runs. Did it fail to fetch from KV? Did the staleness gate fail?
  3. If pulse-sync committed but page is old — check deploy workflow runs. Did Cloudflare Pages deploy succeed?
  4. Manually trigger — push the "Run workflow" button on pulse-sync.yml to attempt an immediate sync from whatever is currently in Apify KV.
  5. Manually trigger Apify — go to the actor page and press "Start". Wait for it to finish, then trigger the GitHub Action.