Human Input

Estimated reading: 6 minutes

The Human Input component enables Human-in-the-Loop (HITL) functionality in Robility Flow by pausing workflow execution until a user reviews information and submits a decision. It introduces a manual checkpoint where a human can evaluate data, choose an action, and control which path the workflow follows next.

For example, a workflow can generate an article draft and pause at a Human Input component for editorial review. Depending on the reviewer’s selection and response timing, the flow routes execution to publish the article, return it for revision, or notify the content owner of a late submission.

How It Works in Robility Flow

1. Robility Flow passes the configured message or upstream input data to the Human Input component.
2. Execution pauses at the component and enters the Awaiting human input state while preserving the current workflow state.
3. A reviewer evaluates the displayed information and submits a response through the supported interface.
4. The component evaluates the submitted choice and response timing, then resumes execution through the corresponding output port.

Configuration

Parameter Description
Input Specifies the message or instructions displayed when the flow pauses. Accepts static text or input from an upstream component and forwards the configured message to the active downstream component.
User Choices* Defines the response options presented to the reviewer. The default choices are Approve and Reject. Additional choices can be added as needed. Each unique choice generates a corresponding output port.
Note: Duplicate choices with the exact same spelling and casing are not allowed. Choices with different casing, such as delete and Delete, are treated as distinct options.
Timeout Specifies the validity window for a human response. Setting this value to 0 disables the component-level timeout. This parameter is available only when Enable Fallback is enabled.
Enable Fallback Specifies the response window in minutes, hours, or days. The default value is 3 Days. This parameter is available only when Enable Fallback is enabled. Set the value to 0 to disable the component-level timeout.

Output

The component dynamically generates output ports based on the configured User Choices* and Enable Fallback settings:

Output Port Condition Description
User Choice Outputs (e.g., Approve, Reject) Generated for each configured choice Routes execution through the branch matching the choice submitted within the active timeout window.
Fallback Generated only when Enable Fallback is enabled Routes execution when a human response is submitted after the configured Timeout period expires.

How the component works

1. When execution reaches the Human Input component, the flow pauses in the Awaiting human input state and displays the configured Input message alongside the available User Choices*.
2. If Timeout is set to a value greater than 0, the component establishes a response validity window based on the configured duration (Mins, Hours, or Days).
3. The flow remains paused until a user submits a response or the platform-level execution limit is reached.
4. Once a response is submitted, the component routes execution to the corresponding User Choice port or the Fallback port based on whether the response arrived within the configured window.

Timeout and Fallback Behaviour

The Timeout parameter sets a validity window for a response rather than acting as an automatic timer. When execution reaches the Human Input component, the flow stays paused in the Awaiting human input state until a user responds or the platform execution limit is reached.

The Fallback port does not run automatically when the timeout expires; it only triggers when a user submits a late response after the allowed window. This prevents outdated decisions from triggering standard approval or rejection branches—for example, notifying a reviewer that a time-sensitive discount has expired instead of applying it late.

Execution Condition Flow Behaviour
Response submitted within the timeout The flow resumes through the output port corresponding to the selected user choice.
Response submitted after the timeout (Fallback enabled) The flow ignores the selected choice and routes execution through the Fallback output port.
Response submitted after the timeout (Fallback disabled) The component rejects the late response and terminates the flow with an error.
No response submitted The flow remains paused until the system execution limit is reached, then ends with an error regardless of the Enable Fallback setting.
Timeout set to 0 Disables the component-level validity window; responses are accepted at any time without routing to Fallback.

Usage Example: Article Approval Workflow

In an article publishing pipeline, the Human Input component requires editorial sign-off before publication while isolating late reviews from the standard publishing path.

1. Add the Human Input component to the workflow canvas after the content preparation step.

2. Configure the parameters as follows:

Parameter Value
Input Review the article and approve publication.
User Choices* Approve, Reject
Timeout 2 Days
Enable Fallback Enabled

3. Connect the generated output ports to the corresponding downstream processes:
Approve: Connect to the publication process to publish the article when approved within 2 days.
Reject: Connect to a revision or notification process to route the article for updates when rejected within 2 days.
Fallback: Connect to a Notify Content Owner component to alert the content owner when a response is submitted after 2 days.

4. Run the flow. When execution reaches the component, it enters the Awaiting human input state and resumes along the appropriate branch once a reviewer submits a response.

Limitations and Execution Controls

1. No automatic timeout execution: The Fallback branch does not trigger automatically when the timeout clock expires; a human response must be submitted after the timeout window to activate the Fallback path.

2. System execution limits: If no response is ever submitted, the flow eventually ends with an error when the platform execution limit is reached, even when Enable Fallback is enabled.

3. Unique choice names: Exact duplicate choices are blocked during configuration. Each option in User Choices* must have a unique spelling or casing.

4. Message forwarding: The component forwards the configured Input message text to the active downstream component.

Troubleshooting

Issue Possible Cause / Solution
The Fallback output is unavailable. Enable Enable Fallback to generate the Fallback output port on the component.
A late response returns an error. Enable Fallback is disabled. Enable it and connect the Fallback output port to route late submissions without failing the flow.
The "Already exists" message appears when adding a choice. A choice with the exact same spelling and casing is already configured. Enter a choice with a distinct spelling or casing.
Share this Doc

Human Input

Or copy link

CONTENTS
Robility Chatbot
Robility Assistant
Online