Join the Webstudio community

Updated 3 months ago

Worker not found screen 🤮

At a glance

The post describes an issue with a screen that appears unstyled and overwhelming for new users, even those who are not faint of heart. The community members suggest adding the provided text directly to the screen, possibly with a diagnostic tool, to explain the reasons why the "Worker can not be found" error may occur, such as not publishing the project after adding a custom domain, the deployment still being in progress, or the domain not being properly connected.

The comments discuss that the main issue seems to be the unstyled appearance of the screen, which may feel daunting for users not accustomed to reading documentation. Community members suggest that styling the text and providing visual aids like GIFs or images to guide users through the fix would be helpful improvements. There is also a discussion about managing errors centrally through the documentation and the possibility of syncing the documentation to avoid maintaining it in multiple places.

One community member created an issue on the project's GitHub repository to address this feedback.

Useful resources
For new users, even someone who is not faint of heart, this screen is just sickening. It feels like something is broken, but it is really just the users impatience (expectations, perhaps), or did not choose a domain when Publishing (like did)

SUGGESTIONS
Just add this text (see screenshot for source) directly to the screen -- maybe with some some diagnose tool?
=================

Webstudio is utilizing Cloudflare's most advanced Edge Publishing network.

Worker can not be found due to one of the following reasons:
  • You haven't published your project after adding a custom domain, learn more about publishing,
  • You clicked on publish, but it is still in the process of deployment, it usually takes 1 minute to distribute your project across the globe.
  • Your domain was not properly connected or you need to republish.
=================
NOTE: Had this sitting in a draft for a while on Discord. Just saw it. Things may have changed since I had this experience last.
Attachments
image_15.png
image_14.png
O
J
11 comments
Is the problem that it looks unstyled?
or is the problem that clicking on a link is too much?
Unstyled. And clicking on a link may feel daunting to someone who is not use to reading documentation or just wants things to feel polished, especially after hitting publish.
That is my guess and my experience. 1 of 1000000 so not science.
I think the text is greate once clicked and if styled would go a long way.
We want to manage errors centrally through the docs, so that's why its not showing right away, but showing error in a polished way should be done
If there was a gif or some images that quicky showed you how to fix the issue. Win.
If you do not want to maintain the documentation in two places, assuming you do not have a way to have a "synced block" (Notion reference), then just stylizing that current text would work for an improvment.
Thanks for the great support from you and the whole team here, by the way. Do not dwell on this item, especially if I am the only one saying it. Just thought it was worth mentioning.
Add a reply
Sign up and join the conversation on Discord