If RoTrail notifications are not showing, open the extension and look at Recent activity first. A recorded change with no desktop banner points to a different problem from a change that was never recorded. This one check can save you from changing browser permissions that have nothing to do with the symptom.
RoTrail records activity before attempting its desktop notification. Quiet hours deliberately stops that notification while keeping the event. Windows and macOS can also silence or hide notifications that an application sends. Start with the event, then follow the delivery path.
Find the change inside RoTrail
Open the popup in the Chrome profile where you watch the account or item. Read Recent activity, then choose View all if you need the full activity page. On that page, clear any search or filters that could be hiding the result.
Look for the specific account or item and the kind of change you expected. A different event arriving successfully does not establish that this category worked. A new display name and a change in item value depend on different observations.
| What you find | What to check next |
|---|---|
| The expected event is recorded, but no banner appeared | RoTrail quiet hours and the operating system's settings for Chrome |
| A banner appeared without a sound | RoTrail's Play a sound setting and the system's sound controls |
| One banner summarizes several profile changes | Group into one alert, then the full activity entry |
| No matching recent event | Watch settings, a usable baseline, data access and successful checks |
| Only an old event is missing | History retention, filters or whether activity was cleared |
An absent old entry cannot tell you whether a banner appeared at the time. Activity has a retention window and an entry cap; it is not a permanent notification receipt. The reviewed RoTrail configuration keeps up to 12 hours on Free, three days on Plus and seven days on Pro, subject to the cap.
If the event exists, check RoTrail's notification settings
Open Settings and find Notifications. Quiet hours uses the computer's local hour. A range from 22 to 8 covers the overnight period, so an event observed at 23:00 can be recorded without producing a desktop notification. Check both the switch and the hour range, especially after travelling or changing the device's clock settings.
For a short test, turn Quiet hours off if you want an immediate visual alert when the next qualifying change is detected. Turning it off does not promise a replay of events recorded earlier in the quiet period. Read those events in activity.
Group into one alert combines a profile's changes from a check into one notification. If several fields changed, counting banners is a poor test of whether every change was recorded. Open the activity entry for the details instead.
Under Background checks, Play a sound controls sound. Switching it off still allows a visual notification and keeps activity. Count on the toolbar icon controls a separate unread count; that count clears when you open RoTrail. Neither a silent computer nor a cleared toolbar count establishes that the event was lost.
Check Chrome's notifications in the operating system
RoTrail sends extension notifications through Chrome. This is separate from allowing a website to send notifications: adding Roblox or the RoTrail website to a list of allowed websites is not the repair for this extension delivery path. Chrome documents the dedicated extension notifications API.
On Windows 11, open Start > Settings > System > Notifications. Check that notifications are enabled, then inspect Chrome's entry among the app senders if it is listed. A sender can be allowed in notification center while its pop-up banners are disabled. Check Do not disturb too, including automatic rules for games, full-screen applications or particular hours. Microsoft explains those controls in its notification settings guide.
On a Mac, open System Settings > Notifications and inspect Chrome's available notification settings. Check whether notifications are allowed and how alerts are presented. Then review the active Focus under System Settings > Focus. A Focus can silence an application even when its general notification setting is enabled. Apple's Notifications settings and Focus guide describe those separate controls.
Make one change at a time and test again. Notification-center behavior and labels vary by operating-system version. If your device does not show the same controls, follow the documentation for its version rather than changing unrelated website permissions.
If no event exists, return to the observation
A desktop notification needs a qualifying recorded change. Confirm the account or item is still watched, that it is active, and that the relevant alert is enabled. Profile-specific settings can override the general choices under What to watch for. Thresholds can also explain why a small follower or value movement produced no event.
A newly added profile needs a starting observation. That first baseline is not a change alert. Later comparisons also need successful data reads; unavailable data is not evidence that nothing changed. Keep the device awake and allow the appropriate scheduled cycle to run. The extension alert delay guide covers the scheduling and request stages in detail.
Do not remove the profile, clear activity or reinstall while trying to understand a recent failure. Those actions can discard the evidence or baseline you need. The profile change tracking guide explains what two successful observations can establish.
Run one useful test and record its result
Use an account you control and an enabled public field, such as its description. After a successful starting observation, make one recognizable change, note the approximate time, and leave Chrome available across the relevant check cycle. Check activity promptly, within its retention period, before judging the banner.
If the event appears but the banner does not, record the event time, Quiet hours setting, active Focus or Do not disturb state, and whether other Chrome notifications appear. Send those details with your installed extension version, Chrome version and operating-system version through RoTrail support. Crop screenshots to the relevant settings or event.
If no event appears, report that outcome instead. Include the affected category and any visible access or data-status message. Never include an access key, password, cookie or security code. A report that says "event recorded at 14:12; no banner; Quiet hours off" gives support a much narrower problem than "notifications broken."
Sources checked 23 October 2026. RoTrail controls and behavior above refer to the reviewed 1.4.0 implementation; compare them with your installed version. This guide does not claim a live notification test on every operating system.