Which of the following is true about long-running workflow?

A long-running workflow is a type of automation process that requires logical fragmentation or human intervention, such as invoice processing or performance reviews1. Long-running workflows are designed as Orchestration Processes in Studio, using the Persistence and Intelligent.OCR package2. This package contains activities that enable the workflow to suspend and resume execution based on certain conditions, such as waiting for a job, a queue item, a form task, or an external task to be completed1. These activities are called persistence points, and they create checkpoints in the workflow where the process state is saved and restored2. In order for the persistence points to work properly, all the variables used in the scope of a long-running activity must be serializable, meaning that they can be converted into a format that can be stored and retrieved3. Non-serializable variables, such as browser or application objects, cannot be used in long-running workflows, as they would cause errors or inconsistencies3.

References: 1: Orchestrator - Working With Long-running Workflows 2: Action Center - Designing long-running workflows 3: Best practice long running processes - UiPath Community Forum