> For the complete documentation index, see [llms.txt](https://manuals.dialox.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manuals.dialox.ai/studio/flows/nodes/iterate-continue.md).

# Iterate: Continue

To break out of an iteration node, this **Iterate: Continue** node can be used. It will stop the iteration and invoke the next node after the iteration. See this example:

<figure><img src="/files/PnSDQvNre1Hk9eFghjZe" alt=""><figcaption><p>Example flow for using continue</p></figcaption></figure>

In the above example, the Flow will iterate the "What can I do for you" node until the user responds that they are done. When triggered, the **Iterate: Continue** step will simply break the iteration cycle and execute the next step after the [**Iterate: Iterate**](/studio/flows/nodes/iterate-iterate.md) node. In this case, it will **Say** "Bye" and then **Control Flow: Close** the conversation.

## Nested iterations

In the simple example above, we could have added the "Bye" and **Control Flow: Close** steps directly inside the "Done" response Flow. However, when using multiple **Iterate** nodes in your Smart App, you may need to use an **Iterate: Continue** node. Consider the following example:

<figure><img src="/files/xjLWh8Xoc4ySWef5Hyjh" alt=""><figcaption><p>Example of using Continue in a nested menu situation</p></figcaption></figure>

From the main menu, the user will enter one of the sub menus. When they have resolved their questions relating to the sub menu they chose, they may want to return to the main menu rather than ending the conversation altogether. The **Iterate: Continue** node will end the current sub menu iteration and fall back automatically to the node that triggered it: in this case, the main menu **Iterate** node above it.

## Resources

* [Iterate: Iterate](/studio/flows/nodes/iterate-iterate.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://manuals.dialox.ai/studio/flows/nodes/iterate-continue.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.