A notification is a short note to one person, stored in the database, shown under the bell and on the Notifications page, and pushed to the phones and browsers that person turned on. How to use them in the panel is in Notifications; this page is how they are made and the rule behind each kind.
Where notifications come from
Two producers write them:
The API, at the moment a contract event happens (drafted, edited, submitted, changed, signed, approved, a signature cleared) and when a share purchase earns the bonus point. These arrive at once.
The worker's detection job, every 5 minutes, which reads data the collector already stored (snapshots, the change log, sort readings, scores, owned analytics, GitHub snapshots, the catalog, the run log, projects and points) and turns what changed into notifications. It sends no request to Roblox or GitHub, so it costs nothing from the collector's budget.
Detection reads rows stamped up to 2 minutes before it runs, since a batch commits a moment after it stamps its rows. After an outage it catches up on at most 6 hours.
Preferences: turning a kind off
Every kind is on by default. In Settings, Notifications each kind has a switch, and each group has Turn all on and Turn all off. A kind you turn off is not stored for you and not pushed; only your choices are stored. Admin kinds are for owners only.
Waits and summaries
Each kind has a wait per subject (a game, a game in a sort, a pull request, a job): a repeat inside the wait is dropped. More than three watchlist alerts of one kind for you in one run become one summary linking to your watchlist.
Watched game: player spike
Player spike, to everyone watching the game: its newest snapshot is at least 1.5 times the mean of the hour before it and at least 200 players more. It needs at least two snapshots in that hour. Wait: 6 hours per game.
Watched game: player drop
Player drop: the newest snapshot is at most half the mean of the hour before and at least 200 players fewer. Wait: 6 hours per game.
Watched game: player record
Player record: the game's observed peak beats the last record reported by 5% and by 20 players, once the game has a day of snapshots. Wait: 6 hours per game. For a studio game every member hears Studio player record instead (not for archived games).
Watched game: game updated
Game updated: Roblox's "updated" time for the game changed. Roblox changes that time often for some games, not only when an update is published. Wait: 6 hours per game.
Watched game: details changed
Details changed: the name, icon, genre, subgenre or price changed. One notice lists every field; a change and back is none. Wait: 1 hour per game.
Watched game enters a sort
Featured in discovery: the game appears in a Roblox sort it was not in at the reading before, or climbs into the top 10 from below. Sponsored placements do not count, and a sort read only once says nothing. Wait: 12 hours per game and sort.
Watched game is breaking out
Breaking out: the game's breakout score reaches 60 from below. It must fall under 50 before it can count again, so a score hovering around 60 stays quiet. Wait: 24 hours per game.
Watched game milestones
Milestone: visits or favorites pass 1K, 10K, 100K, 1M, 10M, 100M or 1B (the highest one passed is named). Once ever per milestone.
Code notifications
- Review requested
Your login is newly among an open pull request's requested reviewers. Wait: 24 hours per pull request.
- Pull request merged
One of your pull requests merged. Once.
- Changes requested
Someone else asked for changes on your pull request. Once per review.
- Release published
A release (not a draft) was published, to every member. Once.
Studio notifications
- Game released
A catalog save moved a studio game to released, or made it public; to every member but the one who saved it. A game registered as already released is not news. Wait: 30 days per game.
- Revenue reported
A new revenue day with more than nothing in it, with the amount, to every member (every member may read studio revenue). Once per day.
Points and shares notifications
- Points earned
A project you developed was released; says your points and the Sunday they last until. Once per project.
- Shares on sale
A game you did not make was released and its pool has shares left; to members who hold none of it. Once per project.
- Share sale closing
That sale is in its last week. Once per project.
- Points expiring
You have unspent points that expire after this Sunday. Once per week.
- Bonus point
From a third member's purchase, told to the developers at once.
Contract notifications
Every developer on a project but the person who acted hears when its contract is drafted, edited, submitted to sign, changed after submission (which clears every signature; those who had signed hear Signature cleared), signed or approved. A developer removed by someone else hears Contract changed ("Removed from ...").
Collector failing and recovered
Owners only. Collector failing: a job's last three runs in the day all failed, or the newest snapshot is 15 minutes old; told once until it recovers (wait 6 hours per job). Collector recovered: its latest run succeeded, or snapshots arrive again (wait 1 hour per job).
Push to phones and browsers
Every stored notification also goes, as a system notification with the studio's icon, to each device its recipient turned on, by standard Web Push. A worker job runs every 15 seconds, takes the new notifications and sends each to each device, so a notification usually reaches a phone within about 15 seconds of appearing under the bell. A tap opens its page. The app icon's badge shows your unread count, and reading your notifications clears it.
What one push run does, exactly
The job takes up to 500 untaken notifications in one UPDATE ... FOR UPDATE SKIP LOCKED, so two
runs never take the same one, and drops those older than an hour. A notification whose kind the
person has turned off since, or an Admin kind for someone no longer an owner, is not sent. Each
remaining one goes to each device, oldest first, eight devices at a time, with a time-to-live of
one day and a Topic from its subject so an offline device keeps only the newest. A device that
fails is sent nothing more in that run.
It works on iPhone and iPad from the Home Screen app (iOS 16.4 or later), on Android Chrome, and on desktop Chrome, Edge, Firefox and Safari. The steps are in Notifications.
Why the iPhone needs the Home Screen app
iOS delivers web notifications only to a site added to the Home Screen and opened from there, not to a Safari tab. In a Safari tab the settings page shows these steps instead of the switch.
Add the panel to the Home Screen
In Safari, tap Share, then Add to Home Screen, then Add.
Open it from the Home Screen
Open Blockout from the Home Screen and sign in.
Turn notifications on
In Settings, Notifications, choose Turn on for this device, then Allow.
Test it
Choose Send a test notification.
What a push carries and what it does not
A push carries only what the notification shows (title, text, its link) and your unread count, encrypted to your browser's keys. Each device is identified by an address from its push service (Apple's, Google's, Mozilla's or Microsoft's; no other is accepted), which is never shown back or logged in full. At most ten devices per person. The service worker caches no page.
When a phone or browser does not get a notification
A notification more than an hour old by the time it is sent is not pushed; it stays under the bell.
A device whose push service refuses rests a minute, doubling up to six hours; ten failures in a row remove it. One the browser unsubscribed is removed at once. What it missed stays under the bell.
An offline device gets only the newest notification of a kind about one subject.
Notification permission refused on the phone: allow it in the phone's own settings.
Related: Notifications in the panel, Collector and freshness, Jobs and queues, Data model.
Updated