Guide

Backend troubleshooting

What to check when forms, logins or images stop working, the backend is paused or still being set up, login emails don't arrive, or a job didn't run.

Last updated Open in ClaudeOpen in ChatGPT
On this page

Start by asking Willo in chat: "is my backend working?" It checks the backend's state and reports it in plain words, including the reason when something is off.

Forms, logins and images stopped, but pages load

This is almost always a paused backend. Your plan includes a monthly amount of backend usage. You get an email at 85% and at 95%; at 100% the backend pauses. Your pages still load, which makes it look like a strange partial outage, but anything that saves or reads data stops, and images stored on your backend stop loading.

Nothing is deleted. The backend comes back on its own on the 1st of the next month (UTC). To bring it back sooner:

  • Move to a bigger plan whose allowance covers what you've used this month, under Billing in your avatar menu. The backend comes back within a few minutes.
  • Ask about a Backend Boost, an add-on that raises the allowance on a paid plan, from Help (the ? at the bottom of the left rail).

If a backend is still paused after the 1st, or after an upgrade, contact support. See Backend usage.

"Your backend is still being set up"

A backend is created when the business's first build starts, and takes a minute or two. Try again shortly. If your business has never been built, it has no backend yet: start the first build.

If you saved a key before the backend was ready, save it again once it is.

Paused or suspended by Willo, or setup failed

These need support, not billing. Contact support from Help (the ? at the bottom of the left rail).

Members aren't getting login emails

The starter sender is meant for testing and sends only 2 login emails an hour for your whole site. Ask Willo "is my login email set up?" and follow Member login and login email to connect your own Resend account.

Already connected?

  • "Pending" for more than a day: check the domain Willo has stored against the domain you own, letter by letter. A typo looks exactly like a DNS problem. Ask Willo to correct it.
  • Resend shows "failed": open the domain's page at resend.com/domains to see which record failed.
  • It worked and then stopped: a DNS record was changed or deleted, or the domain moved provider. Re-check the records at resend.com/domains.
  • The link opens a blank or wrong page: a sign-in link must be opened in the same browser it was requested from. Ask Willo to check the backend's sign-in addresses.

Something works in the draft preview but not live, or the other way round

  • A file missing in the draft: the draft has your storage buckets but none of the live files. Upload a test file in the draft.
  • Members can't sign in on the draft: live accounts aren't on the draft. Sign up as a test member there.
  • A live error that a column can't be found: if the column was added on the draft, it doesn't exist live until you publish. Otherwise the site's code is writing a column the table doesn't have; ask Willo to check the table's real columns and fix the code.

A scheduled job didn't run

Ask Willo "did the job run?". It shows the last dispatch and reads the function's logs.

  • Dispatched, but nothing happened: the function has a bug. Ask Willo to read the logs and fix it.
  • Not dispatched: check the backend isn't paused; paused backends run nothing.
  • Listed as missing: it was removed outside Willo. Ask Willo to recreate it with the same name.
  • Refused when you set it up: the schedule didn't fit your plan's included usage or its most frequent allowed schedule. Use the schedule Willo suggests, or upgrade. See Scheduled backend jobs.

A browser call to a function is blocked

If a page's call to a function fails in the browser with a message about CORS, the function isn't answering the browser's preliminary check. Ask Willo to check the deployed function handles it.

Still stuck

Contact support from Help (the ? at the bottom of the left rail), or email support@willo.ai, with what you were doing and what Willo's check reported.