human-tasks

To pause an automated workflow for human intervention, create a task with a title starting with [HUMAN] and assign it to a human. This blocks the automated workflow and surfaces the task to the orchestrator until the human completes it.

The best way to create a human task for sign-offs is to title it starting with [HUMAN], assign it to a human, and link it to the project human-tasks. This surfaces the sign-off requirement to the orchestrator and blocks progress until completed.

Yes, you can block your own automated task until a user completes a physical action by creating a [HUMAN] task. The workflow remains blocked and notifies the orchestrator until the human task is marked complete.

The orchestrator handles task blocking by halting the automated workflow when a [HUMAN] task is created. It sends notifications to the user and orchestrator upon creation and completion, then unblocks the workflow once the human task is resolved.

Yes, you must follow specific rules: the task title must start with [HUMAN], it must be assigned to a human, and it must be linked to the project human-tasks to ensure proper visibility and routing within the orchestrator.

To minimize back-and-forth during workflow blocking, include clear, high-quality instructions in the [HUMAN] task detailing the specific decision, credential entry, or physical action required for the user to successfully complete and unblock the task.