Hyperflows

Configure execution behavior, prompt handling, and response delivery for Hyperflows across your Aisera tenant.

The Settings > Configuration > Hyperflows configurations control execution behavior, prompt handling, and response delivery for Hyperflows in your Aisera tenant. These are tenant-level settings that apply to all bots you create in this Aisera tenant.

Hyperflow Execution Model

Type	Dropdown
Default	GPT-4o
Requires	Enable Hyperflow V1 disabled

Sets the default large language model (LLM) for Hyperflow execution and testing across your Aisera tenant. Individual applications can override the tenant default when needed. Available models:

• GPT-5.2 — Recommended model for Hyperflow execution. Not available in European deployments.

• GPT-5.1 — Strong reasoning capabilities but can be overly detailed and may terminate conversations prematurely.

• GPT-4o — Reliable performance for standard use cases.

This feature is in beta.

Enable Guided Agent Authoring

Type	Checkbox
Default	Disabled

Enables the guided creation wizard and new prompt editor for newly created Hyperflows. Existing Hyperflows continue to open in the authoring experience they were originally created with, regardless of this setting. See Guided Agent Authoring for a full overview of the new experience.

Stream Hyperflow Response Outputs

Type	Checkbox
Default	Disabled

Controls whether Hyperflow delivers responses progressively as they are generated, including intermediate status updates and output from any sub-workflows it invokes. When disabled, all output is held until execution completes and Aisera silently drops intermediate status messages. Enable this for complex Hyperflows where showing users progress while they wait is beneficial. Requires a streaming-capable channel.

See also: Enable Streaming Flow Response

Max Execution Steps In a Hyperflow

Type	Integer
Default	10

Configure the maximum number of steps a Hyperflow runs before the Aisera Platform stops execution and returns a message to the user. Each step represents one full cycle: the LLM selects a function (API, Action, or Workflow), the function executes, and the LLM receives the result to make the next decision. When the limit is reached without a final answer, the Aisera Platform stops execution. Increase this value for complex, multi-step reasoning chains that require more than 10 function calls. Lower this value to reduce latency and token consumption for simpler flows, or to prevent runaway executions caused by poorly designed tool loops.

The default of 10 applies per execution, not per conversation turn.

No system-enforced upper bound exists. Higher values increase both latency and token consumption per request. When the limit is reached, Aisera does not retry and the user must re-initiate the conversation.