nano SIEM
SOAR

Audit and troubleshooting

Supported in:Self-hosted

Find what SOAR did and why: audit events, run statuses, failure reasons, and fixes for flows that don't fire, runs that fail, and dropped trigger events.

Use the run detail and the audit log to see what SOAR did, who asked for it, and why a run ended the way it did.

What's audited

nano writes an audit event for every SOAR change and every run. Find them at Settings → Audit Log, which needs audit:view. See Platform audit.

AreaAudit actions
Settingssoar_settings_updated, soar_runs_canceled_on_disable, soar_notify_settings_updated, soar_notify_test_sent, soar_egress_allowlist_updated
Catalog and packssoar_catalog_imported, soar_catalog_fetch_refused, soar_pack_installed, soar_pack_upgraded, soar_pack_removed, soar_pack_updates_applied
Connectionssoar_connection_created, soar_connection_updated, soar_connection_removed, soar_connection_tested
Flowssoar_flow_saved, soar_flow_archived, soar_flow_drafted, soar_flow_test_requested
Runssoar_run_requested, soar_run_executed, soar_flow_run_requested, soar_flow_run_finished, soar_run_canceled, soar_playbook_automation_queued
Approvalssoar_approval_decided

Audit events never contain credential values. A pivt draft is audited by its size and outcome, not by the text of the request.

Each run also keeps its own record on Automation → Runs: who or what requested it, the flow version, each step's inputs and outputs with secrets redacted, its approvals with the decider and reason, and the redacted vendor request.

Run statuses

StatusMeaning
queuedWaiting for a worker, a free request slot, or a retry delay
runningA worker is executing a step
suspendedWaiting for an approval
succeededEvery step finished
failedA step failed, or an approval expired. The failure reason says why.
canceledSomeone canceled the run, an approval was rejected, SOAR was turned off, or the run's authority no longer holds
skippedThe trigger was recorded but not run. The runs list and the run trace give the reason: rate limited (the flow's run cap), connection missing, connection ambiguous, pack not installed, flow invalid, schedule invalid or not admitted. Skipped runs are kept 7 days.

Accepted or queued doesn't mean the action happened. Check the step result.

Failure reasons

The run detail shows the failure reason. Steps record the same reasons.

Vendor and action outcomes

ReasonMeaningWhat to do
auth_failedThe vendor refused the credentials or their permissions (HTTP 401 or 403). No change was applied.Fix the credentials or the account's permissions in the vendor, edit the connection, and click Test connection.
rate_limitedThe vendor returned HTTP 429, or the pack's request budget for the minute or day is used upWait, or reduce how often the flow runs.
ambiguousThe request may have reached the vendor, but nano didn't get a clear answerCheck the target in the vendor. nano resends only actions that are safe to retry; otherwise a person must approve a resend.
egress_unavailablenano couldn't open a connection to the vendor under the outbound rulesCheck DNS, your firewall, and SOAR_EGRESS_PROXY_URL if you use a proxy.
invalid_configThe connection's settings are invalid for this actionEdit the connection.
unsupportedThe vendor doesn't support this requestCheck the pack's documentation.
action_failedThe vendor returned another errorOpen the step to see the redacted request and status.
step_attempts_exhaustedThe step reached 32 attemptsFix the cause and start a new run.

Flow and connection changes

ReasonMeaning
pack_version_changedThe pack was upgraded after the run started. Start the run again.
pack_unavailable, action_unavailableThe pack or action was removed or withdrawn.
connection_changedThe connection was edited after the run started. Start the run again.
connection_removedThe connection was deleted.
credentials_unavailable, credentials_invalidnano couldn't open the stored credentials, or they don't match what the pack needs. Re-enter them.
secret_in_inputsA step input contained a connection credential, so nano didn't send it.
action_input_unresolved, action_input_invalidAn input reference had no value, or the value didn't match what the action accepts.
flow_invalid, flow_evaluation, invalid_run, unsupported_moduleThe flow no longer compiles, or an expression couldn't be evaluated. Validate the flow.

Case steps

Case steps have their own reasons, such as case_missing, case_source_scope_refused and case_status_transition_invalid. See Case steps.

Searches, Judge, and notifications

ReasonMeaning
search_query_invalidThe query didn't parse, or named a field that doesn't exist
search_timeoutThe search took longer than 30 seconds
search_too_large, search_admission_unavailable, search_execution_failed, search_unavailableThe search couldn't run or return
search_binding_invalid, search_bounds_invalidA bound value was missing or unusable, or the window or row limit is out of range
judge_budget_exhaustedThe daily token budget is used up. See AI Judge.
judge_timeout, judge_provider_error, judge_unavailableThe AI provider didn't answer in 60 seconds, returned an error, or isn't configured
judge_binding_invalidAn evidence value was missing or too large
notification_cap_reached200 notifications were already sent in the last 24 hours
notification_destination_unknownThe recipient or webhook endpoint isn't configured in Settings → SOAR
notification_changedThe content or destination changed after it was approved
notification_render_invalid, secret_in_notificationThe message couldn't be rendered, or still contained a secret after redaction
smtp_not_configured, smtp_credential_too_short, smtp_auth_failed, smtp_connect_failed, smtp_tls_failedThe SMTP relay isn't set up or refused the message. Check Settings → SOAR and use the test send.

Approvals and authority

ReasonStatusMeaning
approval_rejectedcanceledAn approver rejected the step
approval_expiredfailedNobody decided before the approval expired
approval_authority_revokedcanceledThe approver lost soar:approve or access to the run's data before the step ran
authority_revokedcanceledThe person the run acts for lost a permission the run needs, or can no longer act
authority_missingcanceledThe run has no readable record of who it acts for
source_visibility_revokedcanceledThe person the run acts for can no longer see the triggering alert, its data, or the linked case
playbook_acl_revokedcanceledThe person the run acts for can no longer run the playbook
canceledcanceledSomeone canceled the run
soar_disabledcanceledSOAR was turned off

Troubleshoot

Need help with these checks? Contact support with the run ID and the time with timezone.

A live flow doesn't fire on an alert

Check, in order:

  1. The flow is live, not draft. Only live flows fire.
  2. SOAR is on at Settings → SOAR.
  3. The trigger is Alert committed, and its event match, severity, and rule filters fit the alert. Test the flow with that alert to see whether it compiles for the alert trigger.
  4. The person who last saved the flow can see the alert, including its log source. nano skips a flow for an alert its owner can't see.
  5. The flow still compiles. A pack that was removed, or a Pack default connection on a pack that now has two connections, stops the flow from starting runs.
  6. The flow hasn't already run for this alert. Each alert starts a flow once.

A scheduled flow went back to draft

nano returns a live schedule flow to draft when it can no longer start a run, for example because it no longer compiles or its owner lost a permission. Fix the cause, save, and activate it again.

The Flows page says trigger events were dropped

Trigger events dropped means the trigger queue held 20,000 waiting events and nano dropped new ones. Alerts and cases were still saved, but those events didn't start runs. Narrow your triggers with severity and rule filters and event matches, then run the affected flows manually for the alerts you still need.

A trigger event was dead-lettered

When nano fails to start runs for an event 10 times in a row, it sets the event aside and logs a warning. Dead-lettered events don't start runs. nano keeps them for 7 days, up to the newest 10,000. Fix the cause, then run the flow manually for that alert or case.

A run waits and never finishes

Open the run. suspended means it is waiting for an approval: check Automation → Approvals. The person who started the run, or who last saved a triggered flow, can't approve it; someone else with soar:approve must. If nobody decides, the approval expires and the run fails.

queued for a long time means all workers or request slots are busy. See How runs behave under load.

An action can't be approved

The approver needs soar:approve and an interactive sign-in, can't be the requester, and must be able to see all of the step's data. If source visibility hides any of it, the approver can reject the step but not approve it.

A step says the executor restarted

If a jobs service process stops mid-step, nano reclaims the run after its lease expires, about 16 minutes later. A step that may have reached the vendor is marked ambiguous. A flow run goes back to the queue; a single action fails with ambiguous so a person can check the target first.

What's next

On this page