When a tool does not open
When a tool does not open correctly, the problem is often about access state or route expectations rather than the tool itself.
First check: does this tool require sign-in?
Right now:
- Typing Studio can open publicly
- Code Lab requires sign-in
- Logic Builder requires sign-in
If you try to enter a protected tool while signed out, the platform may redirect you to login first.
Second check: did the route change because of login?
Protected workspaces are designed to keep unauthenticated users out. If you see a login screen, that usually means the route is behaving correctly, not that it is broken.
Sign in first, then try the tool again.
Third check: is the workspace still loading?
Some tools need a moment before they are ready. For example:
- Code Lab may still be preparing the workspace or runtime
- Logic Builder may still be loading the canvas shell
Wait for the main workspace to settle before deciding the page has failed.
Fourth check: return through the tools page
If you are unsure where you landed, restart with the clean entry path:
- go to impanolab.com/tools
- choose the tool card again
- enter from the intended card path
This reduces confusion caused by stale tabs or half-finished redirects.
When to treat it as a real issue
Treat it as a real problem if:
- the tool keeps returning you to the wrong page after sign-in
- the workspace never appears after loading settles
- the page crashes after opening
- a public tool behaves like it is locked
At that point, note what route you opened and what happened immediately before the failure.