Known issues for Splunk SOAR (On-premises)

Release 6.4.1

A list of known issues for SOAR on-premises 6.4.1.

Date filedIssue numberDescription
2025-08-12PSAAS-24911ES blocks fail when the finding does not exist on Splunk SOAR

Workaround: When using a `get finding or investigation` API in an ES playbook block, add an upstream ES block with `refresh finding or investigation` API.

2025-08-11PSAAS-24865Checking for app updates fails when an app has a non-Pythonic version number
2025-07-29PSAAS-24656Refresh finding or investigation returns 500 error

Workaround: No workaround exists.

2025-07-15PSAAS-24475pgbouncer logs are not written to the log file after logrotate
2025-07-09PSAAS-24456Random whois IP action fail
2025-07-07PSAAS-24401Script make_server_node.pyc has hardcoded user 'phantom' and fails with a different one
2025-06-16PSAAS-24136SOAR 6.4.X is using hardcoded path to /opt/phantom/etc/phantom_install.conf in start_phantom.sh
2025-06-11PSAAS-24101REGRESSION: VPE is not showing templates when configuring "promote to case" in Utility block

Workaround: After adding the promote to case utility block, edit the block's Python code. Update phantom.promote() to be:

phantom.promote(container=container, template=<workbook name>)

where workbook name is one of the workbooks listed in /admin/workbooks. Be sure to copy the name exactly. An example would look like this:

phantom.promote(container=container, template="Account Compromise")

Note that after making this change, the VPE will consider this to be custom code.

2025-05-28PSAAS-23958Webhooks querystring parameters are parsed incorrectly
2025-05-19PSAAS-23626Playbook prompt blocks: Response is required, regardless of "Required" field setting
2025-05-15PSAAS-23555SOAR 6.4.0 playbook debugger stuck in Status: Running!

Workaround: Contact Support

2025-04-16PSAAS-23000, PSAAS-22994Join Settings are not copied in copy paste
2025-04-01PSAAS-22727action_result.summary.responder_email datapath is not populated
2025-03-17PSAAS-22485Usernames containing commas (,) cause prompt block execution failures in playbooks
2025-01-16PSAAS-21440VPE: Blocks in top right area of the canvas cannot be selected when there is an error message

Workaround: Move the canvas to a location on your screen where blocks are not obscured by error messages.

To move the canvas, select a blank area of the canvas and drag it to another location on your screen.

2025-01-09PSAAS-21330VPE: Renaming a joined block causes the join settings to be invalid.

Workaround:To update playbooks where you have renamed a block or updated join settings follow these steps.

  1. Open the affected playbook.
  2. In the Visual Playbook Editor, review playbook blocks for which you configured or updated join settings, or have renamed a block. Ensure that the join settings are configured appropriately.
  3. Save the playbook.
2024-02-22PSAAS-16477Podman does not currently work with redirected image URLs due to Docker Hub authentication token changes

Workaround: Manually change the image: line in docker-compose.yaml to point to docker.io/phantomsaas/automation_broker:<$SOAR_VERSION>.