Troubleshooting & FAQ
Most EnClaw hiccups have a thirty-second fix. Find your symptom below; each entry says what's probably happening and what to do. If nothing here helps, your admin (or EnClaw support, for admins) is the next stop.
"The agent didn't answer in my channel"
What's probably happening: the bot isn't in the channel, the channel isn't enabled for EnClaw, or you didn't address the bot.
Work through these:
- Is the bot actually in the channel? In Slack, it needs to be invited (
/invite @EnClaw). No invitation, no ears. - Did you mention it? In an ordinary channel, agents respond to @mentions, not to every message. (In a channel bound to an agent, plain messages work.)
- Is the channel allowed? Organisations can restrict which channels EnClaw participates in — Telegram groups, for instance, work off an allowlist. If the bot is present but stays silent everywhere in that channel, it's likely not enabled there; ask your admin.
- Try a DM. If the bot answers you in a direct message but not in the channel, that confirms it's a channel-level setting, not you.
"The wrong agent replied"
What's probably happening: sticky routing. Once a question of yours is routed to an agent, that agent keeps answering your follow-ups in that channel or DM — great when it's the right agent, mildly annoying when it isn't. See sticky routing for the full picture.
Fix: redirect explicitly. Name the agent you want — "Ask the Project Manager agent to…" — and routing follows your lead from then on. Also worth checking:
- Are you in a bound channel? A channel bound to a specific agent will always answer with that agent; ask elsewhere for a different one.
- Is the question ambiguous? A one-word message gives the Orchestrator little to route on. A clearer ask lands with a better specialist.
"My connector shows expired"
What's happening: the sign-in or token behind the connector has lapsed — they all do eventually, and a password change can end one early. Nothing is broken and nothing was lost.
Fix: open My Connectors, find the card with the Expired badge, choose Re-authenticate, and approve the sign-in (or paste a fresh token for JIRA / Productive.io / GitHub). Your permission toggles are preserved. Details in My Connectors.
This is also the answer when an agent that could read your email yesterday suddenly says it can't today.
"My message got no response at all"
Work through these, in order of likelihood:
- Give it a minute. Complex tasks take time; in Slack, look for the progress message that updates in place — if it's ticking along, the agent is working, not ignoring you.
- Check for a pending approval. A task that needs sign-off waits silently until someone gives it — see the next entry.
- Busy periods queue. When lots of people are asking at once, requests can briefly queue. They aren't lost; they run when capacity frees up.
- Personal agent, wrong audience? A personal agent answers only its owner. If you messaged someone else's personal agent (or expected yours to answer a colleague), that silence is by design.
- Identity not linked? On Slack, EnClaw needs to know which EnClaw user you are. If you've never connected Slack under My Connectors and your Slack email doesn't match your EnClaw account, messages can go unrecognised — link Slack in My Connectors.
- Still nothing? Try the same question in the web app. If it works there, the issue is channel-side — tell your admin which channel misbehaved.
"The agent paused waiting for approval"
Not a fault — a feature doing its job. Actions like sending email or creating a JIRA issue pause for a human yes (why).
Fix: find the approval request and answer it. Check:
- the conversation itself (Slack requests usually appear right in the thread),
- the Approvals page in the web app,
- your email or push notifications.
If the request is waiting on someone else (some actions route to a manager or team owner), a friendly nudge to them is the unblock. And if the request already timed out, it was auto-declined for safety — just ask the agent again and it will raise a fresh one.
"It forgot what I told it"
What's probably happening: context isolation, not amnesia. Each Slack/Teams channel keeps its own separate project context, and each person's memories are private — so an agent won't carry what you said in #project-acme over to #project-zephyr, and it will never surface a colleague's private context to you. See Memory & context.
Fixes:
- Same topic, same channel. Keep a project's conversation in its channel and the agent's memory of it stays rich.
- Restate it where you need it. Telling the agent the fact in the new channel takes ten seconds and sticks.
- Correct it if it's misremembering — "actually, it's X" — corrections overwrite confidently.
- Bear in mind memory keeps the useful distillate, not a transcript; a passing detail from months ago may have faded. Important facts are worth stating clearly ("remember that…").
"I can't find the file my run produced"
Where to look: My Sessions is the "where did my work land" page — find the run, open its detail drawer, and everything it produced is listed under Artifacts, ready to download. The files themselves live in File Space. Runs finish even if you closed your laptop mid-task, so the work is there waiting.
Quick FAQ
Can I stop a task that's already running?
Yes — send stop, cancel, abort or /stop in the same conversation. See Chatting from Slack, Teams & Telegram.
Why did an agent message me out of nowhere? That's a proactive check-in — the agent found something it judged worth raising, like an overdue follow-up. You can tune the frequency or switch it off entirely: see Schedules & reminders.
Can other people see my chats or my memories? No. Your conversation history is yours alone, and personal memories never appear in anyone else's conversations. Organisational memory (shared working facts) is common property by design.
Can an agent send an email without me knowing? Not to speak of — sending email requires approval, and recipients outside your organisation's whitelist are refused entirely. See Approvals.
Why can't my agent do something a colleague's agent can? Usually one of: a skill that isn't switched on for that agent, a connector you haven't linked (My Connectors), or a permission your organisation grants differently. Ask the agent — it will generally tell you which it is.
My scheduled report didn't arrive — where did it go? Check the agent's Scheduler tab in the web app to confirm the schedule is still active, and its logs to see whether the run happened. If the platform was down over the scheduled time, expect a single catch-up run rather than a pile of late ones.
Whom do I contact when this page doesn't cut it? Your workspace admin first — they can see settings and logs you can't. Admins can escalate to EnClaw support. When reporting, include where it happened (channel or web), when, and roughly what you asked — it shortens the hunt enormously.