# Troubleshooting

Diagnose sign-in, authentication, missing targets, quotas, and visible delivery.

Start with one non-sensitive test and keep the client result separate from what is visible on your iPhone.

## The connection cannot sign in

Use the [remote MCP setup page](/agent/mcp) and the same account as your iPhone. Check that your AI client supports remote HTTP MCP and browser authentication. A connection to the public docs MCP only reads published content; it does not connect your account for sending alerts.

For an unattended runtime that cannot open a browser, use an iPhone-approved publishing token with the [webhook API](/agent-alerts/docs/webhook-api).

## HTTP 401

Authentication failed. Check that the credential belongs to this runtime and has not been revoked. Supply it through the runtime's secret store, not a command argument or conversation.

For remote MCP, repeat the client's supported sign-in flow. For token-based publishing, create a replacement connection if the one-time token was lost. Do not log credentials while diagnosing the error.

## No registered target

A `no_targets` result means there is no registered target for the requested surface. Open Agent Alerts on your iPhone, confirm the account, finish onboarding, and review notification and Live Activity permissions. Try one update again after the phone has registered.

## The request was accepted, but nothing appeared

APNs acceptance and visible delivery are different observations. Confirm the account and requested surface, check iPhone permissions, and inspect the returned delivery result. Keep the result described as accepted until you see it on the phone.

Do not create a new activity ID on every retry. Keep a stable ID for the subject, and reuse an idempotency key only for the exact original event.

## The account reached its limit

Check for `quota_limited`, `original_alert_delivered: false`, and `retryable: false`. The original update was not delivered. Do not repeatedly retry a non-retryable quota result.

Free accounts have 350 delivered-alert events per UTC day. Pro accounts, including lifetime Pro, have 3,500. Review [pricing](/agent-alerts/pricing) in the website or the current plan in the iPhone app before changing your workflow.

## A CLI example failed

Confirm that the JSON file is in your terminal's current folder. Use the [Swift CLI installation instructions](/agent-alerts/docs/swift-cli) and the JSON download paired with that gallery example.

CLI content uses `data`; native example state may use `builderData`. The website's downloadable CLI files already make that conversion. An MCP request is a different request shape.

## An approval is still pending

Do not treat waiting, expiry, or a delivery acknowledgement as approval. Poll the exact interaction using the originating connection and inspect the returned response. See [responses and permissions](/agent-alerts/docs/responses-and-permissions).

## Still stuck?

[Email Andreas](mailto:me@andreas.ink) with the client name, the action you tried, the HTTP status or non-sensitive error, and what appeared on your phone. Remove tokens, private payloads, and personal data from anything you share.


Source: https://www.andreas.ink/agent-alerts/docs/troubleshooting
