Freshness and empty numbers

How often each source is read, how quickly new data reaches the panel, what stale and overdue mean, why a number is empty rather than zero, and why times are UTC.

Metrics & data / Metrics and data

Every number is as fresh as the last time its source was read. This page says how often that is, what "stale" means, and why a number can be empty.

How often each source is read

WhatRead
A game's players, visits, favorites and votes (snapshots)Every 5 minutes to every 7 days, by tier
Growth, breakout score and signalsRecomputed every 5 minutes from stored snapshots
Hourly meansRefreshed every 10 minutes
Roblox's discovery sortsEvery 10 minutes
RecommendationsOnce a day per hot, active or warm game
Rolimon's listEvery 10 minutes
Game iconsDaily; cold games' weekly
A creator's other gamesOnce a week per creator
GitHub organization (Code pages)Every 30 minutes
Owned analytics of studio gamesOnce a day, the last 7 complete UTC days

The schedules and what each costs are in Collector and freshness.

How quickly new data reaches the panel

When the worker stores new data it tells the API's read cache, at most once every 30 seconds per kind of data (market, GitHub, studio). The next read after that goes to the database. So a new snapshot shows in the panel within about 30 seconds of being stored.

From a reading to the page. The collector reads Roblox and stores the reading in Postgres. Within 30 seconds the worker bumps that kind of data's version in Redis. The next time anyone opens the page, the API's cache key carries the new version, so it misses, reads Postgres and stores the fresh answer; until then readers get the cached answer, at most 60 seconds old for market data.

The total delay from Roblox to your screen is therefore the game's tier interval (when it was last read), plus up to 30 seconds. How the cache works is in API and caching. A game's page says when it was last read; the Code pages say "Collected 12 minutes ago"; a studio hub says "Roblox's numbers through" a day.

What stale means (Data health)

Owners' Data health page calls a source stale when its newest data is older than about three times its schedule, so one slow run is not an alarm:

SourceStale after
Roblox snapshots15 minutes
GitHub collection1 hour
Owned analytics36 hours

Collector status: Collecting, Behind, Stalled

The Collector page and the Market overview's Collector tile say how collection is going:

Collecting

Snapshots are arriving and no job failed in the last hour.

Collecting with errors

A job run failed in the last hour, or Roblox refused requests since the collector started.

Behind

Some games are more than 10 minutes past their due time. More are tracked than the rate limit allows at the current intervals.

Stalled

The collector is running but no snapshot was stored in the last 15 minutes.

Not running

The API cannot hear the collector at all: its heartbeat, written every 15 seconds, is gone.

Overdue games

A game is overdue when it is more than 10 minutes past its next due read, twice the hot tier's interval. A few overdue games mean the collector is catching up; hot games are always read first.

Empty is never zero

A number nobody could read or compute is empty, shown as a dash or a sentence saying why, never as 0. A 0 is a real reading: a game with 0 players, or growth of exactly 0%.

Why a number is empty

  • Not read yet. A game found a moment ago has no snapshot: its page says "Tracking started. The collector takes its first reading within a minute". On your dashboard a game is waiting until its first reading.

  • Not enough history. Growth needs a reading in the accepted range ("Needs a day of history", "No reading from 1 hour ago yet"). The breakout score and the signals need several complete hours of hourly means ("A game needs eight hours of history before it has any"); volatility needs 12.

  • Too small to score. The breakout score is empty under 100 players.

  • Divided by nothing. Growth from 0 players, a like ratio with no votes, the peak ratio with no peak.

  • Not tracked. A private or unreleased studio game has no public numbers.

  • No key, or Roblox declined. An owned number says why: see Why an owned number is missing.

  • Gone from Roblox. A game Roblox stopped serving (dead tier) leaves every list and loses its growth figures; on your dashboard it is unavailable.

Gaps after an outage

Roblox does not serve history: a snapshot not taken at the time can never be taken later. After a collector outage, growth figures that would span the gap are empty by themselves, and charts draw a straight line between the readings on either side. Read a flat or straight stretch with that in mind.

Times and days are UTC

Every day in the panel is a UTC day, so the server and every browser group the same way: "Today" in notifications, daily charts, owned analytics' days, revenue's "latest full UTC day". Studio weeks and new games each week start Monday 00:00 UTC; the Code pages use GitHub's weeks, from Sunday 00:00 UTC. Players by hour of the week is in UTC hours. "Read 3 minutes ago" is relative, so it reads the same anywhere. The audit log shows times in your browser's time zone, with UTC days in its filter.

Related: Players and CCU, Collector and freshness, Glossary.

Updated