The Collector page (/collector) shows the collector: the process that reads Roblox every few minutes and stores each game's history. It answers "is data still arriving?" How the collector works is on Collector and data freshness.
Who can see the Collector page
The page sits in the Admin rail, which only owners see, but any signed-in member can open /collector.
Everything: the status, tiles, tiers, jobs and requests, each endpoint's last error, the Run history and the raw error texts.
Collector status: Collecting, Collecting with errors, Behind, Stalled, Not running
The Status tile (the accent tile) is one verdict, with a sentence under it:
- Collecting
Snapshots are arriving and no job has failed in the last hour.
- Collecting with errors
Snapshots are arriving, but a job run failed in the last hour, or Roblox refused requests since the collector started. The sentence gives both counts.
- Behind
Games are more than 10 minutes overdue: more are tracked than the rate limit allows at the current intervals.
- Stalled
The collector is running, but no snapshot has been stored for 15 minutes or more.
- Not running
The collector's heartbeat is missing (it expires two minutes after the last one), more than a minute old, or could not be read. History is not being recorded, and cannot be recovered later.
How the status word is decided
The panel takes the first rule that matches, in this order, so a worse state always hides a milder one:
No usable heartbeat: Not running.
No snapshot stored for 15 minutes: Stalled.
Any game more than 10 minutes overdue: Behind.
A job run failed in the last hour, or Roblox refused a request since the collector started: Collecting with errors.
Otherwise: Collecting.
When the collector is down, a red notice says "The collector is down" and the other tiles and cards are hidden; owners still see the run history, which is stored in the database. On a developer's machine it adds the command to start it, pnpm collector:up.
Collector tiles
- Last snapshotseconds
Since the newest snapshot was stored, or None.
- Snapshots in the last hoursnapshots
Snapshots stored in the last hour. The collector's capacity is 30,000 an hour.
- Overduegames
Games more than 10 minutes past their next reading (twice the hot tier's interval).
- Running for
How long the collector has run since it last started, in minutes, hours or days.
Tracked games by tier
The Tracked games card counts the games in each tier, which sets how often a game is read:
| Tier | Read |
|---|---|
| Hot | every 5 minutes |
| Active | every 15 minutes |
| Warm | every hour |
| Cold | every day |
| Dead | every week |
Its footer gives the games in total, those still awaiting a first snapshot, and how many creators are known. Tiers are explained in Tiers and genres.
The collector's jobs in the last hour
The Jobs card lists each job that ran in the last hour, as the collector counts them: Job (with its last error under it), Runs, Failed, Items (games read, sorts walked, rows written), Average time and Last success. When nothing ran it says "No recorded runs in the last hour". Items and Average time are hidden on a phone (shown from 640 pixels wide).
Requests to Roblox per endpoint
Two cards count the requests the collector sent to each Roblox endpoint since it last started (the counts start again at zero on a restart):
- Requests per endpoint
A bar per endpoint, busiest first, with its refusals, errors and bad responses under its name, or "No refusals or errors".
- Requests to Roblox
A table with Endpoint, Sent, Succeeded, Refused, Errors and Bad responses. Owners also see each endpoint's last error under its name.
What a refused request means
Refused counts requests Roblox answered with a rate limit: the collector asked too fast for that endpoint. Errors are HTTP errors and requests that could not reach Roblox. Bad responses are answers that did not have the shape the collector expects. Refusals turn the status to Collecting with errors. How the collector spends its budget: Roblox budget.
The run history (owners)
The Run history is the collector's stored log of every job run, so it outlives a stopped collector and shows when a stop began. Runs are kept for 30 days. Pick the range with the pills in the page header: 24 hours (one bar an hour), 7 days (one every six hours) or 30 days (one a day, the default). The last bar is the current, partial one.
Runs, Failed runs (with their share) and Items handled in the range.
Runs and failures: runs per bucket across every job, succeeded and failed stacked.
Run time per job: each job's average run, in seconds. The busiest 8 jobs are drawn; the footer says how many quieter ones are left out.
Items per run: what each job handled in an average run.
Recent failures: the latest 20 failed runs in the range, newest first, with the job, its error, when, and how long it took.
A line needs runs in two buckets to be drawn; until then the chart says so.
How fresh the Collector page is
The status, tiles, tiers, jobs and requests come from the heartbeat the collector writes every 15 seconds; the page reads it when it opens. The run history is read from the database. Reload the page for newer numbers. Nothing on the page sends a request to Roblox.
The Collector page on a phone
The Status tile takes the full width, and the other tiles sit two to a row (three from 1,024 pixels, five on a wide screen). The range pills stay in the header. Cards stack one under another, the Jobs table hides Items and Average time, and the requests table hides Succeeded below 640 pixels and Bad responses below 768 pixels.
Related: Admin pages, Audit log and Data health.
Updated