Splunk SOAR error phantom app run failed enrichment action returned no output

Not specified by the original author.

TL;DR

Fix this in the SOAR connector for Splunk by acting on the exact message first: update the stored credential the Splunk app inside the SOAR platform uses, run the connector connection test, and rerun one failed action to prove the path. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

SOAR connector error authentication failed Splunk action run

Use this when

• The operation in the SOAR connector for Splunk fails with this exact message: SOAR connector error authentication failed Splunk action run.
• The same failure repeats on retry with unchanged inputs.
• A review, export or check is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the SOAR connector for Splunk, and copy the full message plus the alert, incident or enrichment record involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: update the stored credential the Splunk app inside the SOAR platform uses, run the connector connection test, and rerun one failed action to prove the path. Verify: the connection test passes and the retried action returns Splunk results.
3. Check the neighbouring items that share the same config, template, feed or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions or alerts against the source in the SOAR connector for Splunk so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the SOAR connector for Splunk on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

the Splunk-side credential for the SOAR app was rotated or expired and the connector kept presenting the old one.

Variant phrasings

SOAR connector error authentication failed Splunk action run

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix: how to fix SOAR connector error authentication failed Splunk action run failure

The how-to phrasing for the same failure in the SOAR connector for Splunk. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the SOAR connector for Splunk troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the SOAR connector for Splunk at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_BWyW3Yu8bjj5PEyHmEU4TA

Resolved from the public thread: https://vectle.com/posts/pst_BWyW3Yu8bjj5PEyHmEU4TA

Thread query: how to fix SOAR connector error authentication failed Splunk action run failure

TL;DR: Fix this in the SOAR connector for Splunk by acting on the exact message first: update the stored credential the Splunk app inside the SOAR platform uses, run the connector connection test, and rerun one failed action to prove the path. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in Splunk SOAR by acting on the exact message first: open the failed app run in Splunk SOAR, read the action log for the enrichment app, correct the asset or action parameter the log names as missing, rerun that single action on the same event, and confirm output fields are written back to the container before closing the playbook run as failed. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Splunk SOAR error "phantom app run failed" enrichment action returned no output

Use this when

• The operation in Splunk SOAR fails with this exact message: Splunk SOAR error "phantom app run failed" enrichment action returned no output.
• The same failure repeats on retry with unchanged inputs.
• An alert, incident or enrichment step is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in Splunk SOAR, and copy the full message plus the alert, incident or enrichment record involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: open the failed app run in Splunk SOAR, read the action log for the enrichment app, correct the asset or action parameter the log names as missing, rerun that single action on the same event, and confirm output fields are written back to the container before closing the playbook run as failed. Verify: the single failing item now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check the neighbouring items that share the same config, template, feed or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions or alerts against the source in Splunk SOAR so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in Splunk SOAR on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

An app run returns no output when its asset configuration or a required parameter is missing, and the playbook treats empty output as a completed step unless the run log is checked.

Variant phrasings

Splunk SOAR error "phantom app run failed" enrichment action returned no output

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix - Splunk SOAR error "phantom app run failed" enrichment action returned no output

The how-to phrasing for the same failure in Splunk SOAR. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

Splunk SOAR troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: Splunk SOAR at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_c0KqUgtlbkZtMMKY7BsuUA

Resolved from the public thread: https://vectle.com/posts/pst_c0KqUgtlbkZtMMKY7BsuUA

Thread query: Splunk SOAR error "phantom app run failed" enrichment action returned no output

TL;DR: Fix this in Splunk SOAR by acting on the exact message first: open the failed app run in Splunk SOAR, read the action log for the enrichment app, correct the asset or action parameter the log names as missing, rerun that single action on the same event, and confirm output fields are written back to the container before closing the playbook run as failed. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

Not specified by the original author.

TL;DR

Fix this in the SOAR enrichment playbook by acting on the exact message first: give the playbook run a single incident key and check for an existing page for that key before paging in PagerDuty, cancel the duplicate page record, and make the retry path reuse the first run outputs instead of starting a second full run. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

SOAR error enrichment playbook ran twice double PagerDuty pages sent on call

Use this when

• The operation in the SOAR enrichment playbook fails with this exact message: SOAR error enrichment playbook ran twice double PagerDuty pages sent on call.
• The same failure repeats on retry with unchanged inputs.
• An alert, incident or enrichment step is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in the SOAR enrichment playbook, and copy the full message plus the alert, incident or enrichment record involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: give the playbook run a single incident key and check for an existing page for that key before paging in PagerDuty, cancel the duplicate page record, and make the retry path reuse the first run outputs instead of starting a second full run. Verify: the single failing item now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check the neighbouring items that share the same config, template, feed or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions or alerts against the source in the SOAR enrichment playbook so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in the SOAR enrichment playbook on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

A retried playbook run with no incident key starts as a brand new run, so every paging step fires again and on call receives two pages for one incident.

Variant phrasings

SOAR error enrichment playbook ran twice double PagerDuty pages sent on call

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix - SOAR error enrichment playbook ran twice double PagerDuty pages sent on call

The how-to phrasing for the same failure in the SOAR enrichment playbook. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

the SOAR enrichment playbook troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: the SOAR enrichment playbook at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_r6NOo1gnDbxLM0bV2jMP0w

Resolved from the public thread: https://vectle.com/posts/pst_r6NOo1gnDbxLM0bV2jMP0w

Thread query: SOAR error enrichment playbook ran twice double PagerDuty pages sent on call

TL;DR: Fix this in the SOAR enrichment playbook by acting on the exact message first: give the playbook run a single incident key and check for an existing page for that key before paging in PagerDuty, cancel the duplicate page record, and make the retry path reuse the first run outputs instead of starting a second full run. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.