Troubleshooting

Where the logs are

C:\ProgramData\WorkloadWall:

• workloadwall.log — the app itself (startup, mailbox polling, AI, updates).
• update.log — update checks and installs.
• remote.log, cloudflared.log — remote access.

"It's not loading"

• On the host PC try http://localhost:3000. If that works but other PCs can't reach it, it's the network: the installer opens the Windows firewall for the port, but a third-party firewall may not have been told.
• If localhost doesn't work either: Start menu → Restart WorkloadWall, then check workloadwall.log for the last lines.

Emails aren't becoming tickets

• Admin → Inbox & email — the status chip on the mailbox says when it last checked and shows the last error. Check now runs it immediately.
• Microsoft 365: "401" or "Forbidden" means admin consent wasn't granted or the secret expired. "Not found" on a folder means the path doesn't match Outlook (Inbox/Tickets, not Tickets).
• Mode Unread only skips messages someone already opened. Switch to Everything in the folder for a folder you drag mail into.

Replies aren't reaching requesters

Send test under Outgoing mail. With Microsoft 365, the app registration needs Mail.Send. With Gmail, the password must be an App password, not the account password.

The wall is read-only

The 30-day trial ended. Enter a key under Admin → License; nothing was deleted.

Remote access won't turn on

The Diagnostics panel at the bottom of Admin → Remote access shows the scheduled task state and log tails. The usual cause is a proxy or firewall blocking outbound connections from the PC.

The AI card says "Couldn't triage"

Test connection on Admin → AI intake. Local model: is Ollama running, and is OLLAMA_HOST=0.0.0.0 set so it listens beyond localhost? A cold model can take a minute on the first request — raise the timeout.

Getting help

Screenshot the relevant status box (mailbox chip, Diagnostics, Updates, AI intake) — they're designed to contain what support needs — and the last 20 lines of the log.