Troubleshooting
The symptoms sellers actually hit, and what each one means — most of them are the product being honest.
Most of what looks like a fault here is the extension refusing to guess. Each row below says what the symptom means; where a page explains it properly, it links there.
Numbers that look wrong
| Symptom | What it means |
|---|---|
| Sales show years of history, advertising only about three months | That is the data Amazon serves. See the advertising window. |
| A product shows zero ad spend over a long window | Past the window, zero means not known. The dashboard distinguishes the two; treat them differently, as it does. |
| Today's numbers keep changing | Today is not a complete day. It settles once the day has ended in Los Angeles and been fetched afterwards. |
| Yesterday moved this morning | A cancellation or a return is booked on the day it was observed, not the day the order was placed. The daily curve shows which day moved. |
| The dashboard says a sync is still finishing | Open Data status at the foot of the sidebar: it names the lanes still working. Mid-sync numbers are marked, not guessed. |
Lookouts
| Symptom | What it means |
|---|---|
| A run proposed nothing | Usually working. Preview shows where rows dropped out — the funnel, stage by stage. |
| Everything was held back | A guard fired. The label names which, and the guard is usually right. |
| The run says it matched thousands and deferred | The rule has no max_per_run cap, so it stopped rather than building every row at once. Add a cap — 5,000 is the ceiling — or narrow the condition. |
| A catalogue action never queues | Setting prices, editing attributes and adding products compile and preview, then decline to queue. You can still make those changes by hand — what is not open yet is letting a rule make them for you. |
| A scheduled Lookout ran late | Triggers are floors, not clocks. The run happens the next time Chrome is awake after the interval has passed. |
AI connectors
Each of these is a message you will see in the assistant rather than in the extension.
| Symptom | What it means |
|---|---|
| "No MerchPPC browser is connected right now" | Chrome is closed, or the extension is not linked to your account. Your data lives there, so nothing else can answer. |
| "The connected browser did not respond before the deadline" | The extension is mid-sync. Ask again shortly, or ask for a shorter period. |
| The integration was revoked | Revoked at Account → Assistants. Authorise it again from the assistant. |
| The assistant quota has been reached | 30 calls a minute and 300 a day, shared across assistants. Wait for the window. |
| "This browser is over your plan's device limit" | Choose which browser answers at Account → Browsers. |
Sync feels slow or stalled
The first sync is the long one. Your whole sales history plus the advertising hierarchy; on a large catalogue that is not a thirty-second job. Later syncs are incremental.
The browser was closed. Syncs run in your browser. A closed browser is a paused sync, and it resumes on the next open.
Amazon rate-limited a day. It stays in the retry set and comes back on a later pass. Failed days are never silently skipped.
Still stuck
The Data health tab has a download button that writes out everything the extension knows about its own state — which lanes have run, what is missing, and what failed. Read it first: it says what is actually happening rather than what it looks like.
If you have connected Claude or ChatGPT, you can ask it to report the problem to us. That route runs through our servers rather than through the extension, so it still works when the extension itself is the thing that is broken — which is when a report matters most. The assistant will show you what it is about to send before it sends it, and nothing about your Amazon account travels with it beyond the words you agreed to.