> For the complete documentation index, see [llms.txt](https://help.reasy.ai/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.reasy.ai/help/getting-started/engines/workflow/optimizing-complex-workflows.md).

# Optimizing Complex Workflows

Is your flow too complex to handle? Optimize it using Link Throwing and Link Catching Intermediate Events. They provide the capability to connect two sections of a process. A link event in a flow can “throw” an event that can be “caught” by a catch event. Link Events allow you to pause your flow and check results at that point rather than executing your entire workflow.

Let’s optimize a flow.

* Insert “Intermediate” tools between sections of a process in your flow.
* Change the type of the tool to “LinkThrow” or “LinkCatch”.
* Next, create an event to link them. To create,
  * Click![](https://reasyapps.com/forum/wp-content/uploads/2022/07/Configure.png)in the canvas toolbar, in the Configuration Manager, switch to the **Event Manager** tab, and click **Create event**.
  * Give the event a unique name, select its type, assign a code, and define its scope, whether it can be used only in the current process or in the current application.
  * Add to save the event.
* Then, go to the “LinkThrow” element configuration and select the event. Repeat the same for the “LinkCatch” element to link the flow.


---

# 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://help.reasy.ai/help/getting-started/engines/workflow/optimizing-complex-workflows.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.