Fix Common Issues
Use this guide to identify the class of problem first so you do not waste time applying the wrong kind of fix.
Updated 2026-03-27
Quick Answer
Most Prism issues fall into four buckets: setup, context, permissions, or execution timing. Diagnose the bucket first and the fix usually becomes obvious.
When To Use This
Use this guide when pages are empty, actions feel stale, marketplaces are blocked, or permissions are preventing work.
Prerequisites
You need access to the affected page, the active account and marketplace context, and any visible error text or recent timestamps related to the issue.
Audience
Operators
Estimated Time
6 minutes
Page Type
Troubleshooting
On this page
Use this guide to identify the class of problem first so you do not waste time applying the wrong kind of fix.
Fast Path
Decide whether the problem is setup, context, permissions, or execution lag. Then collect the exact page, account, marketplace, time window, and error text before you retry or escalate.
How To Use This
Most issues sort cleanly into one of these buckets:
- Setup: the account is not fully connected or a marketplace is not ready.
- Context: the wrong account or marketplace is selected.
- Permissions: the role does not allow the action.
- Execution lag: the action happened, but the page you are staring at has not caught up yet.
Start there before you troubleshoot anything more exotic.
What To Watch For
Connect account and Select a marketplace prompts are context problems until proven otherwise.
A successful approval with no visible downstream change is usually an execution-verification problem. Check Activity Log before you conclude the recommendation failed.
Repeated reconnect prompts point to account health, not to dashboard rendering.
FAQ
What should always go into an escalation note?
Include the page, active account, active marketplace, timestamp, filters, exact error text, and the shortest reproducible set of steps.
How long should I wait before calling something a sync failure?
Wait through the normal sync window and check Activity Log first. Declare failure only after you have evidence that execution or sync actually stopped.
Next Steps
Go back to Connect Amazon if setup is the blocker, or use Use Activity Log when the main question is whether something actually executed.
Read next
Related product and trust pages
Sources
Last reviewed by Prism team
