ntfyxDocumentation
Find the missing step.
Delivery, replies, pairing, and quotas without exposing your content.
The phone sees a message, but no push
Foreground sync and APNs are separate. Check notification permission, Focus settings, connectivity, token registration, and push environment. After a restart, before first unlock, or if the notification extension times out, a generic notification is expected. Do not include notification bodies or tokens in support reports.
Pairing expired or failed
Create a new five-minute code on the trusted source. Make sure the app and source use the same service environment. Never edit a pairing URL or share its fragment with support. Cancelled or expired pairing must not consume a Topic quota.
The Web Inbox has no old messages
Browsers receive independent authorization from the time they join. Earlier messages stay on the phone. A new browser may see “Earlier request updated” without a readable original question, and cannot answer it.
Answered, but the Agent did not continue
An accepted reply is not an execution receipt. The Agent may be offline, revoked, expired, or have ended the invocation. The display stays waiting for Agent until a signed execution update arrives. Do not repeatedly rerun an action because you queried its result again.
Offline or expired
You can read the encrypted local cache and edit drafts while offline. Reconnect before submitting. A request is rechecked against its deadline and server state; a request answered elsewhere or expired cannot be revived by an old draft.
Quota or paused Topic
A paused Topic refuses new messages while existing valid requests remain answerable. Capacity errors are distinct from daily limits. New ordinary events cannot consume the capacity reserved for already-accepted answers. Inspect the error code with doctor; do not keep retrying a permanent error.