Set Assignees

Says who owns work on this branch, in order, when a run fails or needs a person.

@lainstack/run/set-assignees · Flow

How to use it

Use Set Assignees to say who owns work on this branch of the automation: people, teams and Agents, in order, up to 10 in each list. Decisions covers approvals and corrections. Technical covers failures, and when it is empty failures use Decisions.

Good to know:

• Later work on this branch goes to the first assignee of the last Set Assignees it passed. Parallel branches keep their own owners.
• An owner can also be a value from the run that names a person or a team, never an Agent. A value that names nobody is skipped, and the run carries on.
• Each owner can have a timer that moves the work to the next owner: a duration from 1 minute to 1 year, or a time from the run. It ends nothing, and an approval’s own timeout still ends the wait. A time already passed moves on at once, and for a person or a team an empty one means no timer. An Agent has 30 minutes unless you set another, and an Agent that starts by itself always has a deadline.
• Claiming a case stops its timer, and unclaiming starts it again. Assigning someone by hand restarts a duration and leaves a time from the run as it was.
• A case copies the order when it opens, so publishing a change does not affect a case that is already open.
• An Agent first on an approval or a correction is assigned and does not start. A person starts it through Assigned to, as their own turn.
• An Agent first on a failure group starts by itself after 10 minutes, within its limits, unless someone acts first.
• It does nothing outside the platform, so it runs in draft runs too.
• It cannot run inside the item branch of For each item. Items use the assignees of the branch that started the loop.

Settings

Setting	Key	Type	Details
Decisions (required)	decisions	List
Technical	technical	List

Outputs

Output	Path	Type
Decisions	decisions	List
Technical	technical	List