Skip to main content

Cycles and Workflows

A project is either a cycle or a workflow. What differs is how it runs. In the Marketplace edition, the default type when you create a project is workflow.

This page explains how each runs and what changes with the type. The criteria for choosing are in the Design Guide.

A workflow runs one item (a case) through and ends​

A workflow runs one execution through the steps in order and ends. In the Marketplace edition this one item is called a case. Steps proceed in series; there are no lanes that split in parallel. At a Branch step, only the lane chosen by the result of the previous step is passed through.

There are four ways to end. Reaching the last step is completed, being rejected at a review step is rejected, a person stopping it is cancelled, and being unable to proceed is failed. In every case, that one item closes there. If it could not be launched, the case ends as failed (Case Guide). To redo a closed case, start a new case.

A cycle keeps running, placement by placement​

A cycle has no start and no end. It runs until you stop it.

Each placement with sweeping enabled runs on the period you set for it. Besides the period, it can also be launched by webhook. It does not wait for other placements to finish. While the placement of one step is running, the placement of another step may be running on a completely different period.

A cycle cannot have a review step, a Branch step, or an External automation step. Build a task that needs a person's judgment, or that sends work to different places by result, as a workflow.

This is where people most often misunderstand. Even if the steps look arranged in a ring, that arrangement is not the order of execution. It is not a mechanism that goes round in turn; think of each running on its own period. A sweep that comes due while the same placement is still running is skipped, and sweeps are not piled up to run later (Trigger Guide).

The biggest difference is the boundary of “one item”​

In a word, the difference between the types is whether there is a boundary called “one item”.

A workflow has a boundary. As a case, you can follow it from start to finish as one unit, so you can tell “what happened to that request”. A case holds its settings and artifacts as versions, and a review step decides by looking at those versions (Case Guide).

A cycle has no boundary. Records are left for every sweep, but there is no “one item” that gathers them. What you can follow is “when what ran”, not “what happened to that request”. What can be placed in a cycle is a registered agent used in chat, and it needs no contract and no certification.