SOAR - playbook not running when new container and artifacts were created

Available Languages

Updated:October 1, 2026
Document ID:SPLK052078

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Applicability

Splunk SOAR

Description

The playbook is set to run automatically on ingested email events. The playbook automation would not execute, even though the events were ingested and containers were created with correct label.


Investigation

The user permission error is in the wsgi.log when processing the container:

{"log_type": "django", "component": "webserver", "product_version": "6.4.1.357", "time": "2025-07-28T12:17:11.184303", "logger": "phantom_ui.ui.models.container", "pid": 1087949, "level": "WARNING", "file": "/opt/phantom/www/phantom_ui/ui/models/container.py", "line": 4981, "message": "Playbook (<playbook_id>) will not run because user (2) lacks the permission to execute it", "ctx_request_id": "88773a4faf6984741acef54e30e8962a", "ctx_request_method": "POST", "ctx_user_id": 2, "ctx_request_remote_addr": "127.0.0.1"...

Resolution

Check the user id "2" from Administration-> User Management -> Users page. In this case, the user is "automation" user. The user was assigned with Automation and asset_viewer roles.

The automation user is a default user in SOAR. By default only Automation role is assigned to the user. Removing the asset_viewer role resolved the issue.

Revision History

Revision Publish Date Comments
1.0
01-Oct-2026
Initial Release

Was this Document Helpful?

FeedbackFeedback

Contact Cisco