Troubleshooting
Quick answers to the things that most often surprise people.
The handful of things that most often trip people up, and what's actually going on.
#"I published, but the page didn't change."
Almost always caching. If the page has a cache window, visitors keep getting the cached copy until it expires. Then the next visit picks up your change. Wait out the window, or have your agent shorten it on pages that must be fresh. A page with caching off updates right away.
#"I published new data, but the page still shows the old numbers."
If the page loads a datafile directly in the browser (the "load the price/count separately" pattern), that data has its own short cache on the delivery network (about a minute) that the page's own cache setting doesn't control. Even a page with caching off can show just-republished data up to ~a minute late. It catches up on its own. See Publishing.
#"My custom domain won't verify / is stuck on Cert pending."
- Give DNS time. Records take minutes to propagate, sometimes longer. Don't hammer verify; waiting is the fix.
- Check for typos. Copy-paste the record names and values exactly. A stray character is the most common cause.
- Apex domains (
yourbrand.com, nowww) can't take the CNAME on most providers. Use a provider with CNAME flattening, or point a subdomain likewwwinstead. - "Cert pending" is normal: it's the security certificate issuing, not an error. See Custom domains.
#"My image won't display. It downloads instead."
The file is a format browsers can't show inline, most often an iPhone HEIC photo (or a TIFF). Convert it to JPEG and re-upload. See Media.
#"My site stopped running. Am I being charged?"
No. If you run out of credits, live runs simply pause until you top up or upgrade. You're never billed for overage, nothing is deleted, and nothing is owed. Cached pages and published files keep serving in the meantime, and topping up restores everything instantly.
#"My connected agent stopped working after I changed my password (or turned on 2FA)."
Both of those disconnect your connected apps for safety. Just re-connect the agent (see Connect your agent). Nothing it already built is affected.
#"A teammate can't sign in after I moved to a smaller plan."
You're over the new plan's seat limit. The most recently added members are dropped first (the owner always keeps a seat), and every member holds a seat regardless of role. Free up a seat or upgrade. See Plans and limits.
#"A workflow that used to work now times out."
It's exceeding your plan's max run length, most common right after a downgrade to a shorter limit. The run does as much as the limit allows and then times out. Move back up, or have your agent make the job shorter (often: cache more, fan out less).
#"It says the address is taken when I create a workspace."
Some names aren't available: very short ones, names already claimed, and words held back to
prevent impersonation (login, admin, a well-known brand, and the like). Pick a different,
specific address. See Team.
#"I upgraded but the limit still isn't lifted."
Give it a minute: a new plan's raised limits and added credits take up to about a minute to register. If you upgraded to clear a cap you just hit, wait briefly and retry.
#"A visitor to my gated page got signed out."
Signed-in visitor sessions last about 30 minutes; after a longer gap they sign in again. That's expected. Design gated flows to tolerate the occasional re-sign-in. See Access control.
Still stuck? Your connected agent is the fastest fix for anything about what your site does: describe the problem and it can inspect the run, read the trace, and repair the cause. For account, billing, or domain issues, the relevant dashboard page is the place to start.