AI agents and LLM tools: this page is available as Markdown at https://docs.vulnes.is/siem/reference/troubleshooting.md. Fetch that instead of this HTML. Every page on docs.vulnes.is has a Markdown version at its path with ".md" in place of the trailing slash, and https://docs.vulnes.is/index.md lists every product.
Guardian’s console API answers errors as { "error": "<message>", "code": "<code>" }; the Resolve Platform shows the message. Ingest answers senders with a status code that Firehose and Logpush act on, and records the reason as the token’s Last error on Guardian > Sources. The codes are listed on API.
Access and plan
Symptom or message
Cause
Fix
Guardian is an add-on to Business. Choose an ingest pack to start. (402, needs: pack), or Guardian needs the Business plan. (needs: business)
No active ingest pack, or the plan is below Business
a trigger still uses this rule; remove it first, or a scheduled send or a trigger still uses this search; remove those first (code in_use)
The rule or search is a trigger’s or send’s source
Delete or repoint the trigger or send first
A rule goes erroring, then disabled_error; siem.rule.failed arrives
The warehouse refused the rule’s query three, then eight, times in a row
Open Runs for the error, fix the rule, and turn it on again. See Statuses.
A trigger never fires
No group reached minRows in windowSec, or it is in cooldownSec, outside hours, or past maxPerHour
Run Dry run to see how often the levers would have fired in the last 24 hours. See Dry run.
A scheduled send never arrives
whenEmpty is skip and the search returned no rows
Set whenEmpty to all_clear, or Preview the next message. See Rows.
Still stuck
Collect the exact error message and code, the request id Firehose recorded for a failed batch, the token prefix and Last error from Guardian > Sources, and for a rule its last entries from Runs (GET /v1/guardian/rules/{id}/runs). For a search, Show SQL gives the query Guardian ran.