Reference
Troubleshooting
Quick fixes for the issues that come up most often while building.
Most problems have a short path to a fix. Here are the ones people hit most, and what to do about each.
A build didn't do what I asked
Usually the prompt was carrying more than one change, or the target was ambiguous. Re-send it as a single, specific instruction — and for a big change, try Plan mode first to agree the approach. If a build went the wrong way, roll back and describe it differently. Rolling back is free.
The preview is blank or erroring
Tell Vorx exactly what you see — "the dashboard is blank after I sign in" — and it will trace and fix it. Include the page and what you clicked just before. See Fixing errors.
My change isn't showing
The preview updates when a build finishes; if one is still running, give it a moment. A hard refresh of the preview clears the occasional stale render.
If the change is missing from your live app rather than the preview, that's expected until you publish again.
An integration isn't working
Most integration issues come down to a missing or wrong key. Check the credential is set under Settings → Cloud → Secrets, and that it's the right one for what you're doing — a sandbox key won't take real payments, and a live key will charge real cards during testing.
There is no call log to read yet (logs and monitoring), so take the error the app shows you and paste it into chat — it usually carries exactly what the provider rejected.
Social sign-in works live but not in the preview
That's expected. Google and Microsoft sign-in only complete on a published URL, because the provider needs a real address to send people back to. Test it on your live site. See Social login.
Builds have stopped starting
You're probably out of credits — building is blocked at a zero balance, though your published app keeps running. Check Settings → Plans & credit usage. On Free, a fresh five arrive the next day. See Plans and credit usage.
A scheduled job didn't run
Open Settings → Cloud → Jobs and check the job's run history. No runs at all means a scheduling problem — check the cadence and say the timezone explicitly. Failed entries mean the function itself is erroring; paste the error into chat.
I can't change something I expected to
Check your workspace role and the project's sharing setting. A Viewer can open a project but not change it, and a project shared as Can view is read-only however you reached it. See Roles and permissions.
Still stuck
The support page has more answers and a way to reach the team.
Next steps
- Fixing errors — describing a break well
- Logs and monitoring — reading what the server saw
- FAQ — the shorter questions