Actions Troubleshooting

This page documents the known action-related problems and the steps to resolve them. Each section describes a symptom, its cause, and the resolution.

Configuring on the Canvas

A Category Is Greyed Out in the List of Actions Panel

When adding an action, one or more categories appear in the List of Actions panel but cannot be selected.

Cause: The canvas enforces the chaining rules at the panel, so a disabled category means the action cannot be added at that spot:

• Operation is disabled when the Flow already holds 10 Operation actions, the maximum.
• Ticketing is disabled when the Flow's trigger is not Anomaly Detected or Anomaly Status Changed, and also when you are chaining from another action instead of from the trigger itself.
• Every category is disabled when the node you are chaining from is a Notification or Workflow action, which ends its branch.

Resolution:

1. For Operation, remove one of the existing Operation actions, or split the pipeline into two Flows chained by an Operation Completed trigger.
2. For Ticketing, add the action directly under the trigger, change the trigger to an anomaly one, or clone the Flow and give the clone an anomaly trigger.
3. When chaining from a notification or workflow node, chain from the trigger or from an Operation, Anomaly, or Ticketing node instead. Ticketing itself is the exception: it only accepts the trigger as its parent.

The Datastore Is Missing from the Datastore Dropdown

An Operation action's Datastore dropdown does not offer the datastore you want.

Cause: Only initialized datastores are listed, across all five operation types. A source datastore becomes initialized after successful Sync, Profile, and Scan runs, while an enrichment datastore needs only Sync and Profile. Export and Materialize narrow the list further: they only offer source datastores that also have an enrichment destination connected.

Resolution: Run those operations on the datastore first, then reopen the panel. For an Export or a Materialize action, connect an enrichment destination to it as well.

A Saved Change Had No Effect

You edited an action and clicked Save, but the Flow keeps behaving as before.

Cause: Save only stores the edit as an unpublished change, marked with a CHANGED badge on the node. The Flow keeps running its last published version until you publish.

Resolution: Click Publish on the canvas. See How a Flow Works for the full lifecycle.

During Executions

An Action Landed as Skipped

In the execution, an action shows the Skipped state instead of running.

Cause: Its parent did not succeed. A downstream action only starts when its parent succeeds, so a failure upstream marks everything below it as Skipped instead of running it. See How Actions Run.

Resolution: Open the execution, find the failed upstream node, and fix what made it fail. The skipped actions run again on the next execution once the parent succeeds.

An Action Failed

An action shows the Failure state in the execution.

Resolution:

1. Open the execution and click the failed node. Its logs describe what went wrong, and the Historical Configuration shows the exact settings the action ran with. See Flow Executions.
2. For a ticketing action, check the ticketing integration connection and credentials; the action fails when the integration is unavailable during the execution.
3. For a notification or workflow action, confirm the destination still exists and is reachable, then use the panel's test button before republishing.

By Action Category

The Anomaly Action Did Not Touch What You Expected

An Archive or Delete action ran but archived or deleted nothing, or it touched anomalies you expected it to leave alone.

Cause: An anomaly only qualifies when it has been untouched for the full Inactivity Period and matches every filled-in filter (AND logic). Any update or comment restarts the inactivity clock, so a busy anomaly is never touched, and a quiet one that matches the filters always is.

Resolution:

1. When nothing was touched, widen the Inactivity Period or relax the filter conditions.
2. When too much was touched, narrow the filters by datastore, status, or tag.
3. If you are missing Duplicate among the archive reasons, that is expected. It requires manually linking a primary anomaly, which an automated action cannot do; pick one of the other reasons.

A Notification Was Not Delivered

The Flow ran, but the message never reached its destination. Pick the tab for your channel.

The Workflow Endpoint Is Not Responding as Expected

A Webhook, HTTP Action, or n8n action cannot reach its destination, or the destination cannot use what it received. Note that Test Workflow is offered on the Webhook and the HTTP Action only; an n8n action has no test button.

Resolution:

1. When Test Workflow fails, check the URL's protocol, domain, and path, and confirm the Auth Type, Username, and Secret match what the endpoint expects.
2. When the endpoint receives calls it cannot trust, set the n8n Webhook Secret (sent as the x-qualytics-secret request header) or use the HTTP Action's authentication, and validate it on the receiving side.
3. When fields are missing from the payload, that is by design. The datastore, operation, and target_link fields are only sent when the trigger provides them, and the context lists arrive empty when the event carries nothing for them. See Payload Structure.

Tickets Are Not Behaving as Expected

Tickets are not being created, not moving to the expected status, or too many are being opened.

Resolution:

1. When the action failed during the execution, check the ticketing integration connection and credentials, then review the execution's logs.
2. When tickets are not moving, confirm the Anomaly Status Changed trigger filters the right status and the Target Ticket Status matches a status that exists in the tracker.
3. When too many tickets are being created, set a minimum Anomaly Severity (Min) and narrow the datastores on the trigger, so each ticket is worth triaging.

Limitations