Troubleshooting
Specific symptoms, and what each one usually means.
The preview is blank or will not load#
The application's container may have been stopped. Start application in the application menu, and give it a few seconds.
If it was already running, ask the builder: the preview is blank — have a look at why.
A build failed#
Say continue. That resolves most of them. See When a build fails.
A build seems to be taking forever#
Watch the steps, not the clock. A build that is working keeps narrating itself — new steps keep appearing — and a large first build legitimately takes a while.
If no new step has appeared for several minutes, that build is no longer running. Within a few minutes it says so and the application comes back to you, ready to be started again from the application menu. Nothing it had already written is lost. Say continue to carry on from where it stopped.
The build finished but nothing changed on the preview#
Two possibilities, in order of likelihood.
Your browser is showing a cached copy — reload with the button above the preview.
Or the change was genuinely not made, because the request was read differently from how you meant it. Read the steps back: they say what it did.
The application cannot see a configuration value I set#
An application reads its configuration when it starts, and the one running was started before you saved it.
On the preview, press Restart the preview in the application menu — or say yes when Settings offers it as you save. On test or live, deploy again; nothing else applies it.
If the name is listed as no value yet, that is the answer: the name is saved and nobody has put the value behind it. Press Replace and paste it in. See Configuration values.
Test or live is showing an old version#
Building does not deploy. A build changes the preview only.
Go to Versions and press Put the latest on Test, or Put what is on Test live. Each card tells you whether it is showing your latest work.
The data I entered in test is not in live#
That is the design. Each environment has its own database, so a version being tested cannot write to what the business is running on. See Environments.
My custom domain is not working#
- Check both DNS records exist — the one pointing the address here, and the TXT record proving ownership.
- Press Verify in Settings › Domain.
- Wait. DNS propagation takes minutes to an hour and cannot be hurried.
- Try the platform address. If that works, it is DNS; if it does not, the application is not deployed.
Visitors are not being counted#
They are only counted for deployed environments. The preview is not counted, because it is your team looking at it.
If a deployment is serving and the number is still zero after a day, tell us.
Somebody cannot sign in to my application#
- Check they are on the list in Settings › Access, and not suspended.
- If they are in the workspace but not this application, either grant them this application or turn on one login for every application.
- Reset their password. It is generated, shown once, and emailed if the application has email connected.
The shared password is not being asked for#
Check which environment you are on. The password is per environment — turning it on for test does not turn it on for live.
I have forgotten my password#
Press Forgot your password? on the sign-in page and you will be emailed a link to choose a new one. It works once and expires after an hour. See Your profile.
This is for your account on the workbench. Somebody who cannot sign in to an application you built is a different account — see Somebody cannot sign in to my application.
An invitation or sign-in code is not arriving#
These come from the platform, not from your application, so Settings › Integrations is the wrong place to look — that is the account your applications send through.
- An invitation. The account was made either way: the Team page says whether the message went. If it did not, add them again with a temporary password instead and read it to them.
- A sign-in code. If you have turned on two-step sign-in and the code never comes, press Start again on the sign-in page and check you typed the right address. If the platform cannot send mail at all, nobody can finish signing in with a code — so turn it on somewhere the mail is known to work.
- A link to choose a new password. The sign-in page says one is on its way whether or not the address has an account, so check you typed the one you sign in with. Only the newest link works, and only for an hour. After three in an hour, no more are sent until the hour is up.
- Check the spam folder either way.
If nothing arrives for anybody, the platform's own mail is not set up. That is for whoever runs it, not for a workspace owner to fix.
An email from my application is not arriving#
- Settings › Integrations — is email connected?
- Press the test. It is a real send to an address that discards it, so a pass means the credentials work.
- If the test passes and the application's email does not arrive, the problem is in what the application does, not in the connection. Ask the builder to look at it.
- Check the recipient's spam folder, and whether your sending domain is verified with the provider.
The tab title is wrong, or a shared link has no picture#
Those are settings, not code: Settings › Appearance. They apply on the next deployment, and on the preview when you Restart the preview. The icon is the exception — it is served in front of the application and changes as soon as you save it. See Appearance.
An old address stopped working#
Settings › Redirects. Add the old path and where it should now go. Served in front of the application, so it works even while the application does not. See Redirects.
The test copy is appearing in search results#
Settings › Search engines — test is closed by default, so it has been opened. Close it.
Note that this asks crawlers not to index it; it is not access control. If it must not be readable, use Access.
I cannot find a setting#
Ask for it. The conversation reaches everything in Settings, so where do I turn on the shared password and turn on the shared password both work. See Asking for settings.
Still stuck#
Tell us the application's name and roughly when it happened. We can see the whole build, including the parts the interface deliberately does not show.