The recruiter-api plugin's announceEvent() sends recruiter cards to Telegram via OPENLOBSTER_CHANNELS_TELEGRAM_TOKEN (its fallback path, since OpenClaw doesn't pass api.bot to "kind: tools" plugins). That env was never set in the container, so every hourly poll threw on the send, events were never marked consumed, and no Telegram notification ever went out — the rest of the "recruiter pipeline has no responses" problem (the GPU/triage half was fixed separately). Wire it from openclaw-secrets.telegram_bot_token (same token as channels.telegram.botToken). Verified: the 3 backlogged events were announced + consumed on the openclaw restart. Drafting (the /api/draft 500 that also degraded the cards) was fixed in parallel by swapping Vault secret/recruiter-responder gpt_mini_model from the slow/timing-out qwen3-coder-480b to meta/llama-3.3-70b-instruct (~1.6s). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| files | ||
| .terraform.lock.hcl | ||
| backend.tf | ||
| main.tf | ||
| providers.tf | ||
| secrets | ||
| terragrunt.hcl | ||