condoo.VibeContacting support
How to reach condoo.Vibe support, what to include so the first reply is useful, and what to try before you write.
If something is not working and the rest of this section has not solved it, get in touch.
Before you write
Two minutes here often saves a day of back and forth, and sometimes solves it outright.
Reload the project
A surprising number of preview and editor problems are a stale browser tab. Reload before anything else.
Check the page for your symptom
The troubleshooting section covers the common failures one by one, including previews that will not load, builds that stall, and deployments that fail.
Try the same thing once more
If a build failed, run it again. A repeated failure is a real fault and worth reporting; a single one is often a transient upstream hiccup that has already cleared.
What to include
Support can only be as fast as the detail allows. A message with these four things usually gets a specific answer first time; one without them usually gets a request for them.
Which project
The project name, and the link to it if you have one open.
What you did
The prompt you sent or the button you pressed, immediately before it went wrong.
What happened
The exact error text if there is one. A screenshot of the whole screen beats a crop, because the surrounding state is often the clue.
When
Roughly what time, and your timezone. That is what makes your session findable in the logs.
Credits and billing
If a build failed and you think you were charged for it, include the project and the approximate time. Charges for work that genuinely failed are put right.
What to expect
You will get a reply with either a fix, a workaround, or a clear statement that it is being investigated. If it is a fault on our side, you will be told when it is resolved rather than being left to check.