I started using Stansa Ai and ran into a problem I can’t figure out on my own. Something changed while I was setting it up, and now it’s not working the way I expected. I need help troubleshooting the issue, understanding what went wrong, and finding the right fix so I can get Stansa Ai working again.
Start with the boring checks first.
- Log out of Stansa AI.
- Clear site cache and cookies.
- Disable browser extensions, esp ad blockers, script blockers, password managers.
- Try a private window.
- Try another browser.
- Check if your model, workspace, or API settings changed during setup.
- Revert any prompt templates, automations, or integrations you added.
- Look at the error log or activity history. Copy the exact error text.
If it broke right after a setting change, roll back one thing at a time. Don’t change five more settings or you’ll lose the trail. Common fail points are wrong API key, revoked permission, bad webhook URL, model switched, or rate limit hit.
If you post these, people here can narrow it down fast:
- Exact error message
- What changed
- Browser and device
- Free or paid plan
- Screenshot, with private info blocked out
Most setup issues end up being auth or permissions. Annoying, but fixable.
One thing I’d add to what @kakeru said: don’t assume it’s your browser right away. Sometimes the problem is just that Stansa saved a bad config state and keeps reusing it.
What I’d check next:
- make a brand new blank project/workspace and test the same action there
- run the most basic prompt possible, like a one-line input with no tools, no memory, no automation
- if that works, the issue is probably in your setup layer, not the core app
- check whether system instructions or custom behavior got overwritten during setup
- verify output limits, temperature, tool access, and attached knowledge files. Weird behavior can come from one tiny toggle
Also, if responses are suddenly worse instead of fully broken, that usuallly means a model/profile swap happened, not a true bug.
If you can, post:
- what it did before
- what it does now
- one exact test case
That diff matters more than people think. Half of troubleshooting is just figuring out what actualy changed.