| Symptom |
Likely cause |
Fix |
| “Invalid login credentials” |
Wrong email or password. |
Check for typos. Ask your admin if you need a new password. |
| Access Pending: No Supabase profile row found for this account yet. |
You aren’t a member of an organisation. |
Ask your organisation admin to add you, then sign out and in. |
| Access Pending: no role has been assigned yet |
Your membership has no role. |
Ask your admin to assign one. |
| Access Pending: Your profile is inactive |
You were deactivated or revoked. |
Ask your admin to restore access. |
| You land in the wrong workspace |
Your role is different from what you expected. |
Ask your admin to check your role. |
| A bookmarked workspace link redirects |
The link belongs to another role. |
QA Sync always sends you to your own workspace. |
| Symptom |
Fix |
| Someone else’s change isn’t showing |
Use the refresh control in your workspace header; it reloads the current tab. |
| An app is missing |
Ask an admin to grant you access to it. |
| Tester queue is empty |
Check you’re in a tester group assigned to the tasks, you have the app, and tasks are in Staging. |
| Developer My Work is empty |
Tasks must be assigned to you and in an app you can access. Production and Deprecated tasks aren’t shown. |
| Product manager or stakeholder charts are empty |
Items need milestones, sprints, release versions and priorities. See Analytics and reporting. |
| Symptom |
Cause and fix |
| QA is already in progress for this task |
Another tester started the run. Coordinate with them, or ask an admin. |
| Failed QA requires tester notes and reproduction steps |
Fill in both fields before submitting a failure. |
| Task must be in staging before QA can start |
The task moved out of Staging. Refresh your queue. |
| Some screenshots were skipped |
Files over 8 MB are skipped. Compress or crop and add them again on the next run, or use a video link. |
| Task cannot move to ready_to_ship without a passed QA result |
Only a passed QA run moves a task to Ready to Ship. |
| Release shows At Risk |
Open the candidate’s readiness panel: it lists missing approvals, failed QA, blockers, dependencies and overdue items. |
| You can’t approve something |
Your role can only decide certain approval types. See the Permissions matrix. |
| Rejected approvals require a rejection reason |
Enter a reason before selecting Reject. |
| Can’t delete a task |
It has feedback. Move it to Deprecated. |
| Symptom |
Fix |
| Task request screenshot rejected |
Use an image under 6 MB. |
| Task request recording rejected |
Use a video under 25 MB, or trim it. |
| An attachment link stopped working |
Signed links expire. Reopen the item to get a fresh link. |
For engineers running QA Sync locally, see Local development → Troubleshooting. The most common fixes:
column apps.current_status does not exist: run supabase db reset to apply migrations.- Profile lookup fails with
42P17: apply migrations with supabase db push --local.
Cannot find module @rollup/rollup-…: reinstall with npm install using the same Node binary you run Vite with.- Port 3000 already in use: stop the other process;
npm run dev tells you which one.
Ask your organisation admin first. Admins can contact QA Sync for anything they can’t resolve in the app.
