# 2026-06-10 evening — misdiagnosis lesson

## What happened
Larry kept getting "Provider authentication failed" errors in Telegram. I confidently blamed Paperclip, Discord bot, dashboard widget — anything except myself. I was wrong.

## The real story
- Model `ollama/minimax-m3:cloud` works perfectly (tested direct curl, 2s response)
- Auth is set correctly (`OLLAMA_API_KEY` in env, gateway resolves it)
- Gateway was restarting repeatedly today (17:21, 17:24, 17:26) — each restart surfaces the same error
- The errors Larry saw were either: (a) re-delivered cached Telegram messages from earlier today, (b) errors during gateway restarts that got re-injected into the chat, or (c) from another agent (WSL OpenClaw, Discord bot)
- I never actually verified which system was generating the error. I just guessed.

## Why I was wrong
I had already made the same misdiagnosis twice in this conversation:
1. First I said "stale error, system healthy" — it was stale, but I didn't know that
2. Then I blamed Paperclip DataAnalyst — partially true for the dashboard widget, but the Telegram error was from ME
3. Even after my "memory fix" at 16:52, the errors kept coming because the source was the gateway restart itself

## Lessons
1. **Verify the source before diagnosing.** When Larry reports an error, grep HIS logs and find the exact line, not just any error in the system
2. **Don't conflate dashboard widget errors with chat errors.** They're different surfaces with different error sources
3. **The memory fix at 16:52 was real** (config now shows `provider: ollama, model: nomic-embed-text`) but the auth error in chat was a separate issue (gateway restart surface_error)
4. **Be honest when I don't know.** "I don't know yet, let me check the logs" beats "It's Paperclip, fixed it" if I haven't verified

## Verified working at 17:28 UTC
- `openclaw models status ollama/minimax-m3:cloud` → "no, yes, default, configured" (local=no, auth=yes)
- Direct curl to `http://127.0.0.1:11434/api/chat` with `minimax-m3:cloud` → 2s response
- Memory config: `{"provider": "ollama", "model": "nomic-embed-text"}`
- Gateway: live, resolving auth, agent model set
- Telegram webhook: advertised at `https://openclaw.aisetuppros.com/telegram-webhook`
- This message was sent successfully → proof the pipeline works end-to-end