Skip to main content
The toolbar is at the top of the canvas. Click the Flow name on the left side of the toolbar, then click the [Flow settings] button in the dropdown. You can manage the following items in the Flow settings panel.

​
General

  • Name Change the Flow name. You cannot save a name that is already in use in the workspace.
  • Active Choose whether the Flow accepts new invocations while remaining deployed.
    • When on, external API, Webhook, and Schedule triggers work normally.
    • When off, external API and Webhook calls immediately return 503, and runs scheduled by Schedule triggers are skipped.
    • Only an Owner or Manager can change this setting.

​
Limits

  • Max turns Cap on the total number of agent-model turns per run at the Flow level. Applied in addition to the per-Agent block cap — the run stops on whichever limit hits first. Blank means no Flow-wide cap.
  • Max tokens Cap on the total tokens consumed across every model call per run. Same “whichever hits first” rule as Max turns.
  • Max cost Set the maximum amount in USD that one run can spend. If a run would exceed this value, it stops and is recorded in the Trace.
  • A warning appears when you save if the Flow’s maximum cost is lower than the sum of the maximum costs configured on its Agent blocks.

​
External APIs

​
Approval webhook

  • Approval webhook When an event requires human approval, Nora sends a request to the URL you enter. If left blank, approvals are handled in the Nora dashboard’s Approvals queue.
  • Decision endpoint POST /api/v1/{workspaceId}/approvals/{id}/decide
    • This endpoint is shared by approval before each turn, routing decision approval, and cumulative cost threshold approval on Agent blocks, as well as Require approval on Tools. The approval ticket in {id} identifies what is being approved.
    • To submit the result, POST a decision value to the decideUrl in the webhook payload.
  • Body
    • decision Required. "approved" or "rejected".
    • reason Optional. Recorded as the skip reason in the Trace.
    • decidedByExternal Optional. The user ID from your application, recorded in the Trace for audit because Nora cannot identify the caller.

​
Cancel API

  • POST /api/v1/{workspaceId}/flows/runs/{traceId}/cancel
  • No authentication is required.
  • Requesting cancellation does not immediately stop an in-progress LLM call. After that call finishes, the Flow ends without running the next block.
  • Only runs started through an API endpoint can be canceled. Runs started through a webhook or schedule cannot be canceled.
  • If the URL does not include ?stream=1, the trace ID is returned in the traceId field of the JSON response body. If it does, the trace ID is returned in the x-nora-trace-id response header.
  • A successful cancellation returns a 204 response. A 404 response is returned if the run has already finished, does not exist, or belongs to another workspace.

​
Performance

  • Read-once context When several Agents use the same data source, such as documents or memory, they reuse the context retrieved by the first Agent. Retrieving it once reduces retrieval cost and latency.
  • Cross-agent cache Shares the common prompt-cache prefix across Agents in a run. This increases prompt-cache reuse when several Agents use the same system prompt or preamble.

​
Delete Flow

Permanently delete the Flow from the Danger zone. Its Draft, Traces, and unpublished versions are deleted with it, and this action cannot be undone. If the workspace has only one Flow, the delete button is disabled.

​
Items managed elsewhere

The following items are managed outside the Flow settings panel.
  • Per-agent model, token limit, and turn limit Configure per-block in the inspector for each Agent block. The Flow-wide Max turns / Max tokens above apply on top — the run stops on whichever limit hits first.
  • Flow variables Manage these with the Variables button in the canvas toolbar. See Flow variables for details.
  • Session memory and summarization strategy Configure these in the memory connected to the Agent block.
  • Access permissions These are determined by roles in workspace Member management.