> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/ja/action-basics/notifications/troubleshooting-notifications.md).

# 通知のトラブルシューティング

私たちには、通知の問題をトラブルシューティングする際にチェックすることをお勧めするいくつかの要件があります。

**通知は、以下の条件を満たす場合にのみ送信されます。**

1. アプリ（AndroidまたはiOS）のビルドを作成している場合
2. 送信先の対象者（"受信者"に設定されたユーザー）が存在する場合

**通知は、以下の条件を満たす場合にのみ受信されます。**

1. 受信者がデバイスにアプリをインストールしている場合
2. 受信者がログインしているか、過去2週間以内にアプリでアクティビティを行っている場合にアクティブと見なされます。
3. 受信者が許可された権限（通知権限）を持っている場合
4. 受信者が通知をトリガーしたユーザーでないこと。つまり、ログインしているユーザーが自分自身に通知をトリガーしていないこと。

{% content-ref url="/pages/z67GXUQ7Po7MzzLKfvYm" %}
[Androidで通知が動作しない](/ja/action-basics/notifications/troubleshooting-notifications/notifications-not-working-on-android.md)
{% endcontent-ref %}

{% content-ref url="/pages/kqU7h8oIcwbZzq0vIC55" %}
[iOSで通知が動作しない](/ja/action-basics/notifications/troubleshooting-notifications/notifications-not-working-on-ios.md)
{% endcontent-ref %}

{% content-ref url="/pages/IiQ3Nu2FsDu6byhwqsrZ" %}
[PWAで通知が動作しない](/ja/action-basics/notifications/troubleshooting-notifications/notifications-not-working-on-pwa.md)
{% endcontent-ref %}


---

# 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.adalo.com/ja/action-basics/notifications/troubleshooting-notifications.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.