> For the complete documentation index, see [llms.txt](https://docs.frends.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frends.com/release-notes/frends-6.2/new-features.md). # New Features New features introduced in Frends 6.2 In addition to the following completely new features in Frends 6.2, you can also [check out the release notes for version 6.2.0 here](/release-notes/frends-6.2/version-6.2.0.md) and [the breaking changes here](/release-notes/frends-6.2/breaking-changes.md). ## Long Running Processes Long running Processes is a new feature which allows for Processes to he paused or suspended while waiting for work being finished elsewhere or resuming execution after an error for a critical Process. This allows for designing workflow where human interaction is required and a way of presenting a full workflow in one Process instead of splitting the Process up into multiple subparts. The paused Process will be persisted into the Agent database and it can be signalled to resume when signalled from another Process is received or in a scheduled fashion. It is also possible to resume a Process manually from the UI with modified context, which allows modifying erroneous data afterwards. [You can learn more about the Long Running Processes from here](/frends-development/integrations/long-running-processes.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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.frends.com/release-notes/frends-6.2/new-features.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.