Troubleshooting
Symptoms, in the order they come up. Connector-specific problems have their own page.
The agent did the wrong thing
Section titled “The agent did the wrong thing”Read the run before changing anything — the tool calls show where it went wrong, and the fix follows from that.
| What you see in the run | Cause | Fix |
|---|---|---|
| It called no tools and answered from general knowledge | It does not know it should look something up | Say so in the system prompt; check the connector is bound |
| It called the right tool with wrong arguments | Missing context | Put the fact in the prompt or memory |
| It looped without converging | Task underspecified, or effort too low for its length | Narrow the task; raise effort |
| The answer is right but unusable | No stated standard for “done” | Describe the output you want in the prompt |
| It asked you something obvious | The fact is not anywhere it can see | Prompt, memory, or project |
If one steering sentence reliably rescues the run, that sentence belongs in the prompt. See Testing and iterating.
The run is not finishing
Section titled “The run is not finishing”It is paused, waiting for you. A question, an approval, or a skill request holds the run indefinitely. Scroll to the bottom of the conversation — the prompt is there.
It hit the step limit. Long tasks end without a final answer. Ask it to continue, or split the task.
It failed. The error is in the conversation. A model error usually means the model provider rejected the call — with BYOK, check the key and its credit.
You closed the app. That does not stop anything. Runs finish on Endue’s servers and the result is in the thread when you return.
Nothing happens when I send a message
Section titled “Nothing happens when I send a message”- A run is already going. A message sent during a run steers it rather than starting a new turn.
- You are out of allowance. Runs are declined when the week’s allowance is exhausted — see Plans and usage.
- You were signed out. Sessions end after a period of inactivity; sign in again and the conversation is where you left it.
The agent lost a capability it had
Section titled “The agent lost a capability it had”| Symptom | Check |
|---|---|
| A connector’s tools are gone | The connection needs re-authorizing, or was unbound — see Troubleshooting connections |
| It stopped remembering things | The memory tool group may be switched off |
| It stopped saving artifacts | The artifact tool group may be switched off |
| It behaves like an older version of itself | A prompt revision may have been restored |
Changes apply to the next run. An agent that ignores an edit you just made is probably mid-run.
A routine is not running
Section titled “A routine is not running”- It was paused after repeated failures. Endue pauses a failing routine and notifies you rather than retrying forever.
- It ran and refused an action. Unattended runs cannot send or delete — see Routines.
- It ran and you did not notice. Check the inbox; output usually lands as an artifact.
Getting help
Section titled “Getting help”- Search these docs — press Ctrl/⌘ + K from any page.
- Email us — [email protected]. Include what you asked for, what the agent did, and which tool call went wrong; that is usually enough to answer without a back-and-forth.