# Why did an agent stop before completing every requested step?

Canonical URL: https://help.iagenify.com/faqs/agent/why-did-an-agent-stop-before-completing-every-requested-step

[← Back to Agent FAQs](https://help.iagenify.com/faqs/agent)

HELP CENTER · FAQ Agent 2 min read
# Why did an agent stop before completing every requested step?
A stopped run does not always mean the agent ignored part of the request. The stop reason and recorded steps help distinguish a configured limit from a tool problem or an intentional stop.
IaGenify
Agent

## Read the recorded steps and stop reason
Open the run result and inspect the steps the agent completed, including any tool errors and summaries. Compare the final recorded action with the task: the agent may have finished the essential work but omitted a requested check, or it may have stopped while waiting on an unavailable capability. Use the recorded stop reason as evidence rather than guessing from the final text alone.
An agent can be configured with a maximum number of steps. A complex task that needs research, edits, and verification may reach that limit before every part is complete. Increasing the limit gives the agent more opportunities to act, but it does not guarantee correctness and may allow it to continue down an unhelpful path.
## Adjust the task before simply increasing the limit
If the run stopped at its step budget, split the request into a clear next stage or increase the limit only when the remaining work is understood. Narrowing the task can reduce unnecessary tool calls and make progress easier to inspect. Preserve the run context or summarize completed work so the next attempt does not repeat actions already taken.
If a tool returned an error, address that cause before retrying. More steps will not fix missing access, invalid inputs, or a service that is unavailable. After the next run, check that the requested outcome and its verification both appear in the recorded work. [← Back to Agent FAQs](https://help.iagenify.com/faqs/agent)