Updating BizNode

BizNode separates two things that must never be confused: code and data. Updates only replace code. Your data never moves.

The two buckets

Think of your BizNode folder like a restaurant: the kitchen equipment can be upgraded without touching the recipe book and customer orders.

The table below shows every item in your BizNode folder and what happens to it during an update.

The update.ps1 script accepts the following parameters:

.\update.ps1 -NodePath "C:\Users\YourName\BizNode"

.\update.ps1 -NodePath "C:\Users\YourName\BizNode" -Restart

.\update.ps1 -NodePath "C:\Users\YourName\BizNode" -NewDeps

.\update.ps1 -NodePath "C:\Users\YourName\BizNode" -NewDeps -Restart

After restarting, confirm the update applied correctly:

1. Check the dashboard version

Open your dashboard at http://localhost:7777. The version number in the footer or Setup section should match the release you installed.

2. Check container status

Open a terminal in your BizNode folder and run:

docker compose ps

All services (bot, dashboard, qdrant, ollama) should show running state. If any show Restarting, check the logs for that service.

3. Check service logs

# Bot logs (last 50 lines)
docker compose logs --tail=50 bot

# Dashboard logs
docker compose logs --tail=50 dashboard

Look for a clean startup sequence with no ImportError or SyntaxError messages.

4. Run the status check

python status.py

This checks all services (Ollama, Qdrant, dashboard, bot) and reports their health. All should show OK.

5. Send a test message to your bot

Open Telegram and send /start to your bot. A response confirms the bot container is up and the update is working end-to-end.

PowerShell says "cannot be loaded because running scripts is disabled"

Windows blocks unsigned scripts by default. Run this once in an elevated (Administrator) PowerShell, then retry:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

update.ps1 reports robocopy errors (exit code > 7)

Exit codes 8 and above from robocopy indicate a real failure (e.g. file in use, access denied). The most common cause is a Docker container holding a lock on a Python file. Stop the containers first:

cd "C:\Users\YourName\BizNode"
docker compose stop bot dashboard

Then run update.ps1 again, then docker compose start bot dashboard.

Bot does not respond after update

Check the bot logs:

docker compose logs --tail=80 bot

Common causes:

• New Python package needed — run update.ps1 -NewDeps
• Docker image needs rebuilding — run docker compose build bot && docker compose up -d bot
• Syntax error in updated code — the log will show the exact file and line

Dashboard shows a blank page or 500 error

docker compose logs --tail=80 dashboard

If you see ImportError, a new dependency is likely required:

docker compose build dashboard
docker compose up -d dashboard

Database error on startup: "no such column"

This means a new column was added to an existing table in this release. The release notes will include an ALTER TABLE migration command to run once:

# Example — run this in your node folder
python -c "
import sqlite3, os
db = sqlite3.connect('memory/biznode.db')
db.execute('ALTER TABLE tablename ADD COLUMN newcol TEXT DEFAULT NULL')
db.commit(); db.close()
print('Migration done')
"

Exact commands for each migration are always listed in the release notes.

Accidentally ran update.ps1 with wrong NodePath

Want to roll back to the previous version

Re-run update.ps1 from the previous BizNode release ZIP, pointing it at your node folder. Code files are simply overwritten again with the older version. Database and settings are not touched by either operation.