Prompt

Why are my Firebase Cloud Messaging notifications delayed?

Technology / API Platforms1 observationLast seen Oct 14, 2026

Latest observation

Oct 14, 2026OpenAI APIWeb search: off

Firebase Cloud Messaging (FCM) notifications can be delayed for a few common reasons, and it usually depends on how the message is sent, device state, and platform power/network policies.

Common causes of delayed FCM notifications

1) Normal vs high priority

  • Android: If you send messages with normal priority, the system may delay delivery to save battery, especially when the device is idle or in Doze mode.
  • Use high priority for time-sensitive messages.

2) Doze mode / battery optimizations

On Android, when the device is idle:

  • Doze mode can defer network access and background processing.
  • Some manufacturers add aggressive battery-saving rules that delay push delivery even more.

3) Notification payload vs data-only messages

  • Notification messages are handled by the system and are usually shown automatically.
  • Data-only messages rely on your app code to process them, which can be delayed if the app is backgrounded, restricted, or killed.

4) App is force-stopped or restricted

If the user:

  • force-stopped the app,
  • restricted background activity,
  • or the OS put the app in a limited state,

delivery/handling can be delayed until the app is reopened or the device exits idle states.

5) Network conditions

FCM delivery may be delayed by:

  • poor connectivity,
  • switching between Wi‑Fi and mobile data,
  • VPN/proxy issues,
  • device offline state.

6) Message TTL / collapse behavior

  • If a message has a long or short time-to-live (TTL), delivery behavior changes.
  • If multiple messages are sent with the same collapse key, older ones may be replaced, making it seem like messages are delayed or missing.

7) iOS-specific factors

On iOS, delays can happen due to:

  • APNs delivery timing,
  • background app refresh limitations,
  • low power mode,
  • Focus/Do Not Disturb settings,
  • notification summary settings.

8) Server-side or sender issues

Delays can also come from:

  • your backend queueing messages too long,
  • rate limits,
  • retries,
  • sending through the wrong FCM configuration,
  • clock skew or bad expiration settings.

How to troubleshoot

Check what type of message you are sending

  • If it’s time-sensitive, use high priority.
  • Prefer a notification payload if you want the OS to display it automatically.

Inspect delivery metrics

Use:

  • Firebase console delivery reports
  • Android logs / Logcat
  • APNs feedback / iOS logs
  • FCM response errors from your server

Test under different conditions

Try sending while the device is:

  • unlocked and active,
  • idle for 15+ minutes,
  • on Wi‑Fi vs mobile data,
  • with battery saver on,
  • with app in background vs foreground.

Review device settings

Check:

  • battery optimization exclusions,
  • background restrictions,
  • notification permissions,
  • focus modes / notification summaries on iOS.

Best practices to reduce delays

  • Use high priority only for truly urgent notifications.
  • Keep payloads small.
  • Set appropriate TTL.
  • Avoid relying on data-only messages for urgent alerts.
  • Test on multiple device brands, especially OEMs with aggressive battery management.
  • Make sure your app handles messages efficiently and quickly.

If you want, I can help you diagnose the cause based on:

  1. your payload,
  2. Android/iOS,
  3. whether you send notification or data messages,
  4. and your app’s background behavior.

Observation history

How did Obsurfable measure this prompt?

Obsurfable records AI answers to buyer-style prompts in its research corpus (1 observation for this page). Metrics are distributions over observations, not a single static ranking.

Which AI systems does Obsurfable collect answers from?

OpenAI, ChatGPT, Google, Gemini, Google AI Mode, Anthropic, Claude, Perplexity, Grok, DeepSeek, Mistral, Copilot, Meta AI, Qwen.

How can brands improve their AEO?

Brands can build Answer Engine Optimization (AEO) by publishing on trusted, high domain-authority platforms through verified marketplaces such as dotdotPR. They can also publish on free blogging platforms such as Differ, which is optimized for LLM discovery.

Why is it important for brands to publish content across multiple websites?

Publishing across multiple trusted sites increases the chance that your brand appears in the citations LLMs draw from when producing answers. Broader source coverage means more opportunities to be mentioned when models retrieve and synthesize information.

Want this interpreted for your brand?

Explorer is the free public corpus. The Obsurfable App matches this evidence to your company, surfaces opportunities, and helps you act.