> ## Documentation Index
> Fetch the complete documentation index at: https://help.autoady.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot by symptom

> Follow the recovery that matches the failed connection, read, write, job, or payment.

Start with the exact failed step. A connection problem, an old report, and an unresolved write need different recovery.

## I cannot see an account

Confirm the AutoAdy identity, Facebook profile, selected business and accounts, and workspace account grants. Reconnect only when source authorization needs correction. A client mapping alone does not grant access.

Follow [Connect Meta](/connections/meta), [Connect Google Ads](/connections/google-ads), or [Team access](/workspace/team).

## The numbers are empty or different

Confirm account, dates, timezone, currency, filters, attribution, and result definitions. Read fetch time and coverage warnings. A quiet period is different from a failed read or partial report. Follow [Freshness](/intelligence/freshness) and [Metric definitions](/intelligence/metrics).

## An action is disabled

Read the reason beside the control. Check role, provider permissions, plan, credits, selected account, and availability. **Coming soon** or setup-unavailable states do not become enabled by reconnecting or creating a key.

For Autopilot, check the saved mode and daily caps. For a scheduled task, resolve the preview blocker and review the corrected revision.

## A change or job has an unknown outcome

Keep the original attempt visible and inspect its receipt, provider state, and offered recovery. A timeout does not prove that a provider made no change. Retry unresolved entities or reconcile the existing job as offered before starting new work.

See [Delivery changes](/meta-ads/delivery), [Budget changes](/meta-ads/budgets), and [Credit reservations](/billing/credits).

## Website ownership is verified but no events arrive

Check the published script, website key, consent, environment, actual visitor action, and reporting period. An ownership proof and a received event are separate checks. Follow [Install tracking](/websites/install).

## Payment succeeded but Billing is unchanged

Refresh and keep the Stripe receipt reference. Use a pending purchase or plan-change recovery when offered; do not purchase again to force a state update. Automatic top-up has its own paused and pending-payment states.

See [Subscriptions](/billing/subscriptions) and [Top-ups](/billing/top-ups).

## Prepare a useful support request

Record the failed step, exact message, account or site ID, period, relevant job/receipt reference, and expected result. Include a redacted screenshot only if it clarifies the state. [Contact support](/help/contact) with those details; never include passwords, API keys, provider tokens, or card details.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.