nano SIEM
SOAR

Limits and safety

Supported in:Self-hosted

Every limit SOAR enforces, which ones you can change, how runs behave during an alert storm, and how to keep automation safe.

Plan your flows around the limits below. nano enforces each one; a flow or request that exceeds a limit is refused with a message that names it. Most limits are fixed. The ones you can change say how.

Runs and execution

LimitValueCan you change it?
Runs executing at once8 for each jobs service processFixed
Vendor requests in flight at once16 for each processYes: SOAR_MAX_CONCURRENT_EXCHANGES, 1 to 256
Wait for a free request slotUp to 10 seconds for a single action. A flow step doesn't wait. In both cases the run stays queued and tries again.Fixed
Time for one action step15 minutesFixed
Time for one vendor request1 to 60 seconds, set by the packSet by the pack
Vendor requests per packSet by the pack, up to 600 a minute and 200,000 a daySet by the pack
Attempts of one step32Fixed
Retries of one action1 to 5. Constant delay of 1 to 300 seconds, or a growing delay from a 1 to 60 second base with a multiplier of 1 to 300.Per step, within these bounds
Run inputs256 KiBFixed
Recorded output of one action256 KiB. Larger output is recorded as truncated.Fixed
Recorded output of a run240 KiB. Larger output is recorded as truncated.Fixed

SOAR_MAX_CONCURRENT_EXCHANGES is read from the environment of the nano API and jobs services when they start. A value outside 1 to 256, or one that isn't a whole number, falls back to 16.

Flows

LimitValueCan you change it?
Flows500, not counting archived flowsFixed
Steps in a flow64Fixed
Nesting depth4 levelsFixed
Items in one loop100Fixed
Loop items in one run100, across all loopsFixed
Loop orderItems always run one at a time, in order. From v2.0.33 the editor no longer offers parallel loops.Fixed
Parallel branchesNot supported. A flow with them fails validation.Fixed
Flow definition1 MiB and 20,000 valuesFixed
Triggered runs per flow (from v2.0.33)60 per rolling hour by default. Extra triggers are recorded as Skipped · rate limited and kept 7 days. Manual runs don't count.Per flow, up to 1,000, under Limits
Circuit breaker (from v2.0.33)Pauses the flow after 5 failed triggered runs in a row, or above 600 triggers in an hour. A run whose approval expired unanswered doesn't count as a failure.Spike threshold per flow, under Limits. Resuming needs soar:manage and a reason.
Triggers held while paused (from v2.0.33)Up to 100, replayed oldest first after you resume the flowFixed

Triggers

LimitValueCan you change it?
Runs per eventOne run of each matching flow for each alert, case event, or triage verdictFixed
Schedule intervalAt least 5 minutes between runsPer flow, within this bound
Event matchUp to 8 clauses and 8,192 bytesFixed
Rules in an alert triggerUp to 64 rule IDsFixed
Trigger queue20,000 events waiting. New events beyond that are dropped and counted.Fixed
Retries of a trigger event10 attempts, waiting 5 seconds and doubling up to 5 minutes, then the event is set aside (dead-lettered)Fixed
Dead-lettered events kept7 days, newest 10,000Fixed

Steps

LimitValueCan you change it?
Search time windowUp to 30 daysPer step, within this bound
Search rows1 to 1,000Per step, within this bound
Search time30 secondsFixed
Search queryUp to 64 KiBFixed
Search output240 KiB. Rows beyond that are left out and the output is marked truncated.Fixed
Judge token cap2,000 by default, up to 8,000 per callPer step, within this bound
Judge evidence1 to 32 values, 32 KiB togetherFixed
Judge labels1 to 32Fixed
Judge timeout60 secondsFixed
Judge cache6 hours by default, up to 24 hoursPer step, within this bound
AI Judge daily token budget250,000 by default, 0 to 1,000,000,000Yes: Settings → SOAR
Approval wait1 minute to 24 hours for an approval gate (default 24 hours). 24 hours for an action or notification.Per approval gate, within this bound
Approval choicesUp to 32Fixed
Approval reasonUp to 2,048 charactersFixed

Notifications

LimitValueCan you change it?
Notifications sent200 in any rolling 24 hours, email and webhook together, including test sendsFixed
Email recipients50Fixed
Webhook endpoints50Fixed
Subject200 charactersFixed
Body template8 KiB. Rendered body up to 16 KiB.Fixed
Values bound into a notification16, each up to 200 charactersFixed

Connections and outbound traffic

LimitValueCan you change it?
Connections256Fixed
Credential fields64 per connection, 16 KiB eachFixed
Private-network allowlist64 entriesFixed. You edit the entries on Settings → SOAR.
Outbound destinationsPublic addresses only, pinned for the run. Private hosts only through the allowlist, for packs marked for self-managed tools.Allowlist only
RedirectsNot followedFixed
Air-gapped catalog age30 days by defaultYes: SOAR_OFFLINE_INDEX_MAX_AGE_DAYS, 1 to 90
Vendor calls per connection (from v2.0.33)60 per minute by default, across every flow. A step that finds the minute full waits for the next minute.Per connection, up to 600

How runs behave under load

During an alert storm, SOAR works through runs in order and doesn't merge alerts. From v2.0.33, a flow's run cap and circuit breaker bound how many runs one storm can start.

  • One run per alert per flow. If a rule fires 1,000 alerts and two live flows match each one, nano starts 2,000 runs.
  • Runs queue. Each jobs service process executes up to 8 runs at once. The others wait in the queue and start oldest first as workers free up. A run that waits for approval doesn't hold a worker.
  • Vendor requests share a pool. At most 16 requests to vendors are in flight per process. A flow step that finds no free slot goes back to the queue and tries again.
  • Packs have budgets. When a pack's request budget for the minute or day is used up, its steps fail with rate_limited instead of piling up requests.
  • The trigger queue has a ceiling. If 20,000 events are already waiting, nano drops new trigger events and counts them. The Flows page shows Trigger events dropped with the count and the last time. Alerts and cases themselves are always saved.
  • Approvals pile up too. Each run that needs approval creates its own approval.

From v2.0.33, each flow has a triggered-run cap and a circuit breaker (see Flows). Flows and connections that existed before the v2.0.33 upgrade show No limit (set before upgrade) for the caps until you tick Apply the default limits; the failure breaker applies to every flow. Scope your triggers anyway, so a storm can't flood your queue or your approvers.

Keep automation safe

  • Scope triggers tightly. Filter alert triggers by severity and rule, and add an event match on the entities you care about. Severity and rule filters are checked as the alert is written, so an alert that no live flow wants never enters the trigger queue. See Triggers.
  • Gate disruptive actions. Put an approval gate, or Always require approval, in front of anything that contains hosts, suspends users, or blocks traffic. Destructive actions always wait for a person.
  • Require approval on notifications you want to review. From v2.0.33, an email step waits for approval unless you choose Send without approval. Webhook steps send without approval unless you set approval: required.
  • Test before you activate. A test with a real alert shows what each step would do without changing anything. See Test a flow.
  • Use a dedicated owner. A flow acts for the person who last saved it. Save production flows from an account whose permissions match what the flow should do, and have someone else approve.
  • Prefer actions that are safe to retry. nano resends an action after an unclear outcome only when the pack marks it safe to retry. Otherwise a person decides.

What's next

On this page