> For the complete documentation index, see [llms.txt](https://docs.work-relay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.work-relay.com/automations/best-practices-screensteps/review-advanced-process-types/need-review-and-merge-types-of-flows.md).

# (need review and merge) Types of flows

## Recurrent flows

Recurrent flows are typical business processes that are relatively stable and are executed over and over. For example, a job requisition process.

To build recurrent flows:

{% stepper %}
{% step %}

## Create the flow

{% endstep %}

{% step %}

## Specify a trigger for the flow

Specify what conditions are needed for the flow to execute (e.g. add a new record to the flow data source, like the job requisition object).
{% endstep %}

{% step %}

## Create a flow instance

Every time a flow is triggered, a new instance (record) of the flow is created.
{% endstep %}
{% endstepper %}

## Project flows

Project flows:

1. Are designed to be executed just once.
2. Are manually associated with a specific data record.
3. Are unique in their flow structure.
4. Allow users to plan start and end dates for steps, and entere revised dates as the flow progresses.
5. Are likely to change often as the flow progresses (e.g. add steps on-the-fly).

Project flows are a hybrid between project management and process management. One-time flows are by definition unique - they each have their own dates, and tasks/steps can be modified while the flow is in progress.

Project flows are built as follows:

{% stepper %}
{% step %}

## Create a template flow

{% endstep %}

{% step %}

## Create a record

Create a record for the data source specified in the template flow settings.
{% endstep %}

{% step %}

## Open Flow Builder

Click "Flow Builder" from the record page.
{% endstep %}

{% step %}

## Select a flow template

Select the flow template you want to use for this record.
{% endstep %}

{% step %}

## Clone the template

The system clones the flow template, and the cloned flow is now linked directly to just this one record.
{% endstep %}

{% step %}

## Enter dates

Click "Gantt" to enter dates for steps, etc.
{% endstep %}

{% step %}

## Start the flow

Click "Start Flow" when you are ready for the flow to begin.
{% endstep %}
{% endstepper %}

## Recurrent versus project flows

The primary difference between Recurrent and Project flows is that you would use aProject flow if you want to include planned and revised dates, and you want to have complete control over the flow steps for a particular flow instance.

Everything works the same way, except that for Project flows:

1. A record is created first.
2. Then a flow template is selected.
3. Planned Start and End Dates are entered through the Gantt interface.
4. The flow is started manually.
5. The flow steps can be changed at any time during the execution of the flow.

With Recurrent flows:

1. A flow has a start type/condition (e.g. a record is added, a field is updated, the start is scheduled).
2. The flow starts when the start condition occurs.
3. Only the sequence of the flow can be changed once the flow begins.
4. If other changes are required once the flow begins, the flow can be terminated and a new flow can pick up from where it was terminated.