> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-notifications-troubl-2.md).

# Mobile Client notifications do not arrive from the server

Diagnose server and cloud settings that prevent Mobile Client notifications.

1. **Site internet to cloud active** - load `https://commandcentre-ap-southeast-2-res.security.gallagher.cloud/health` in a browser. Expect a "Healthy" result.
2. **Command Centre can reach the cloud** - Configuration Client → Cloud item under Services and Workstations → Advanced tab → **Test Connection**. Expect success. Failure indicates a networking issue.
3. **Notifications enabled for the user:**
   * **Mobile Connect:** the phone needs a valid registered **Mobile Credential** (Command Centre client → Cards tile → credential shown and valid).
   * **Command Centre Mobile:** the phone must be a valid **enrolled Mobile Device**. If they can log on with operator name and password, it is enrolled. A **Notification Filter** must be created for the alarms to notify, assigned to the cardholder, and enabled.
   * Log off the app and back on. The unique notification token is sent to the server during logon.
4. **Check the Command Centre server logs** for cloud-related connection failures or security errors.

***

🔗 **Related**

* [Notifications - Troubleshooting a Mobile Device](/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-notifications-troublesho.md). The device-side checks for the same problem.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.security.gallagher.com/knowledge-hub/products/cloud-services/command-centre-mobile-client/troubleshoot/mobile-client-notifications-troubl-2.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.