> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/developer-guides/error-messages/0203-to-0227/aur0226.md). # AUR0226 ## Error Message `AUR0226: Maximum number of recursive effect run reached. Consider handle effect dependencies differently.` ## Description This error occurs when an effect re-triggers itself repeatedly (directly or indirectly) until Aurelia’s recursion safeguard stops it. This usually means the effect both depends on and mutates the same observed state (creating a feedback loop). ## Example Trigger ```ts // ❌ Effect writes to the same state it reads this.observation.run(() => { this.count = this.count + 1; }); ``` ## Solutions * Avoid writing to reactive dependencies inside the same effect that reads them. * Split responsibilities: compute derived values without side effects, and trigger side effects from explicit actions or separate effects with different dependencies. ## Troubleshooting * Identify which assignment inside the effect causes the re-run and refactor it out. * Use logs/breakpoints to see which dependencies are being observed. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.aurelia.io/developer-guides/error-messages/0203-to-0227/aur0226.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.