Grafana Cloud
Last reviewed: November 9, 2026

Troubleshoot the Grafana mobile app

Fix the problems most often reported with the Grafana mobile app.

Push notifications aren’t arriving

First, confirm you’ve added push notifications to your personal notification rules. Refer to Configure push notifications for setup steps and a Send test notification option that confirms delivery end to end.

If test notifications don’t arrive, check for these causes.

Notification permission

The app asks for permission to send notifications as soon as you finish signing in for the first time. Push notifications work from then on, without restarting the app. If you denied the prompt, allow notifications for the Grafana app in your device settings.

Test notification messages on Mobile API accounts

On accounts connected through the Mobile API, the app shows a message after you send a test notification:

  • Test notification sent means Grafana Cloud sent the notification. If it doesn’t arrive, check the device causes on this page.
  • This device wasn’t registered for notifications means Grafana Cloud had no record of this device for the account. The app registers the device again, so wait a moment and send another test. If the message keeps appearing, check that notifications are allowed for the app in your device settings.
  • Too many test notifications means you sent several in a short time. Wait a moment and try again.
  • Couldn’t send a test notification means the request failed, for example because your device is offline. Check your connection and try again.

Refer to Test notification results for Mobile API accounts for more about these messages.

Android permissions

Open Settings > Push notifications and look for a device permissions check that flags common delivery problems:

  • Battery optimization: confirm battery optimization is turned off for the app.
  • DND permission: allow Grafana to override Do Not Disturb.
  • Unused app restriction: turn off your device’s unused app setting, for example, Manage app if unused. Otherwise Android can pause the app after a few months without use, and a paused app doesn’t receive notifications. Refer to On Android in Configure push notifications.
  • Auto Start: on devices that support it, confirm Auto Start is turned on.

Tap any flagged item to open the relevant system settings screen. Exact menu names and available options vary by Android device manufacturer and OS version.

The app creates the notification channels for a stack as soon as you sign in to it, so you don’t need to restart the app before you configure them in your device settings.

Registration failures on Home

If the app can’t register your device for push notifications at all, for example because it couldn’t reach the internet during setup, a banner titled You might not receive Push Notifications appears on Home. Tap Try again to register again, or tap Contact us to send feedback if the problem continues.

On accounts connected through the Mobile API, the same banner appears when the app couldn’t register your device with one of those accounts. Tap Try again to register it again.

A stack shows Login expired

A connected stack’s session can expire over time. When it does, the stack shows Login expired in Connected accounts. Tap the stack to sign in again. Refer to Connect and switch stacks for the ways to open Connected accounts.

After you sign in again, the app reloads that stack’s data. Connect to the internet to load fresh data before using it offline. Your other connected stacks keep their own sessions and cached data.

Saved Home panels are kept for the same verified user and organization. If the previous owner cannot be verified, those panels remain stored but hidden from the new login.

Data looks out of date when you’re offline

The app caches recently loaded alert groups, schedules, and incidents on your device, so you can still see the last loaded state after you lose your connection. If a request fails, for example because your phone loses signal, the screen shows a connection error message with a Retry option instead of clearing what you already loaded.

Push notifications and any actions you take, such as acknowledging or resolving an alert group, still require an internet connection to reach Grafana IRM.

An incident notification has missing details

In notification history, an incident notification without a title shows Incident updated. Status and severity changes appear only when both the previous and current values are available. If the notification has no incident identifier, tapping it doesn’t open an incident.

Notification history also shows test notifications and notifications whose linked item was deleted or is unavailable. These entries show the original title, message, and time. They do not open a detail page.

A section is missing from Browse

Start with Settings > Products, because turning a product off hides everything belonging to it. Grafana IRM covers the IRM section, with alert groups, schedules, and incidents. Dashboards covers the Dashboards section, and Assistant covers Conversations in the Assistant section. Browse itself disappears when both are off. Refer to Choose which products you see.

If the product is on and a section is still missing, what you see depends on the Grafana IRM permissions your organization has granted you. Check with your Grafana Cloud administrator if you expect access you don’t have.

Dashboards don’t appear or don’t load

If there’s no Dashboards entry under Browse and no Starred dashboards section on Home, open Settings > Products and confirm Dashboards is turned on.

If a dashboard shows Couldn’t open Grafana, check your connection and tap Retry. If it keeps failing, tap Contact us. The same options appear when Assistant can’t load its embedded page.

If a dashboard shows Your stack isn’t responding, or stays on a black or loading screen and then shows that message, your Grafana Cloud stack might be paused or still starting. Stacks can pause after a period without use. Tap Open in browser to open the dashboard in your device’s browser, which wakes the stack, and then tap Try again in the app. The app also retries on its own a couple of times before it shows the message.

If the page shows Sign in again, retry first. If the problem continues, sign out of the affected account and sign in again. Switching accounts or signing in again clears the previous embedded session before loading the selected account’s content.

You don’t sign in separately for dashboards, and there’s nothing to configure. Refer to Dashboards on mobile for details.

Next steps