Troubleshooting

The problems people actually hit, with the fix for each. If yours is not here, say "send feedback to mixshift" in the chat and describe it; that reaches the team directly.

"Not signed in" or brands stop loading

Sessions refresh automatically, but a long-idle machine can drop one. Say "sign in to mixshift" and run the 30-second flow again. If a scheduled task (not a person) hit this, see Run unattended and scheduled tasks; the fix-it path there re-anchors its credential.

Install fails or loops on Windows

Antivirus scanners can briefly lock files mid-install and the marketplace add fails partway. Retry the install; it succeeds on a clean pass. If it keeps happening, add an exclusion for your Claude plugin folder and retry.

A command worked, but ended with "Assertion failed" on Windows

On Windows with Node 24, older versions of the plugin could finish a command that had worked by printing Assertion failed: !(handle->flags & UV_HANDLE_CLOSING) and exiting as if it had failed, which could also hide the "a newer version is available" notice. That was a Node.js bug on Windows, triggered by how the plugin exited after a network request. Update the plugin and commands exit cleanly with the right code and the update notice shows again; see Keep the plugin updated.

Commands will not run at all

Check Node.js: run node --version in a terminal; the plugin needs version 20 or newer.
On a personal Claude plan, make sure code execution is turned on under claude.ai Settings, Capabilities.

I updated but nothing changed

A running session keeps the version it started with, and starting a new chat or session does not pick up the new one. Fully quit the application and relaunch it. If the old version still shows after that, an earlier copy of the application is usually still running in the background and still serving the old build; close that one too. Asking to update the plugin will report the build this session is running alongside the build installed on your machine, which tells you whether the update landed or only the relaunch is outstanding. In Cowork, if the plugin panel still shows an old version label afterward, remove and re-add the marketplace entry; your sign-in and settings survive.

A report came back failed

When Amazon refuses a report, the reason Amazon gave now appears right under the failure message, for example that the start date must be a Sunday or that a daily vendor report can cover at most 15 days. Change the one thing it names before trying again. The date rules are the same every time: weekly reports run Sunday to Saturday, monthly reports cover a whole month, vendor daily reports cover at most 15 days, and the newest few days are not ready yet. Two Brand Analytics reports, Alternate Purchase and Item Comparison, have been retired by Amazon and always fail; the report list marks them as retired.

My query result arrived as a file instead of in chat

That is deliberate. Large results save as CSV files with a short preview so the conversation stays usable and nothing is truncated. Ask for the file contents inline if you really want them in chat.

A report pull seems stuck

Some Amazon report types generate slowly on the Amazon side (AMC especially: minutes, not seconds). The skill keeps polling and reports when done. Let it finish; cancelling and resubmitting just restarts the queue.

A skill says it needs brand context

That skill reads a brand profile. Run brand setup once for that brand and re-run.

Still stuck?

"mixshift help" routes you from inside the chat.
"send feedback to mixshift" files the problem with the team.
Or email support@mixshift.io.