Troubleshooting
Most problems are easiest to fix by just describing them in the app's chat — "the delete button doesn't work" is enough, you don't need to diagnose it. For issues that persist, here's what's going on and how to get unstuck.
"It saved but reads back empty" or "the data isn't there"
The app's database is separate from the file tree. If the agent saved data but reads back nothing, the fix is usually a schema or query issue, not a deploy issue. The agent can run a read-only query_db to see exactly what's stored and correct the mismatch.
The app renders blank
A blank page usually means a missing or broken asset reference, or a JavaScript error on load. The agent's verify() smoke test and render_screen (a real browser screenshot) catch these before a build finishes — but if you hit one after editing by hand, asking the agent to "check the console" or run a UI test will surface the exact error.
A build won't finish
A build can't complete until verify() passes — meaning the app actually loads cleanly in Cloudflare's runtime. If a build is stuck, the agent has the real errors and is iterating on them; the message stream shows what it's trying. Saying "what's blocking the build?" gets a plain explanation.
Custom domain stuck on "pending"
Custom domains are provisioned through Cloudflare for SaaS and depend on DNS being configured correctly at your registrar. The app shows the exact DNS records it needs; once those propagate (and the certificate issues), the domain goes active. If it's stuck, the platform can probe the live DNS and tell you precisely what's misconfigured — ask in chat.
The app is slow or hits a size limit
If the agent warns the app is approaching its Worker size budget, the fix is to move large embedded data (seed JSON, big text blobs) into the database, KV, or R2 instead of keeping it inline in source. Ask the agent to do that and it will.
A change worked in preview but not after publishing
Drafts and published apps run in the same isolated environment, so a working preview should carry over. If something differs after publishing, it's usually stale content rather than a code change — ask the agent to re-verify and re-deploy, and it will re-run the smoke test.
Still stuck?
Describe the symptom plainly in chat — the agent has full memory of the app it built and can inspect files, database, and live logs directly. If the problem is on Nexrall's side rather than your app's, contact support@nexrall.com.