When using "startAction" Flow API in a Business rule (any server-side script), it doesn't seem to run as system - Known Error

When using "startAction" Flow API in a Business rule (any server-side script), it doesn't seem to run as system Description When using "startAction" Flow API in a Business rule (any server-side script), it runs asynchronously, but doesn't run as system as an asynchronous business rule would.

Steps to Reproduce

Steps to reproduce: Run the below script from the Scripts - Background in OOB instance: (replace the table name and sys_id with appropriate values) *** (function() { var inc = new GlideRecord('incident'); inc.get('sys_id of any incident record'); try { var inputs = {}; inputs['ah_task'] = inc; // GlideRecord of table: task inputs['ah_comment'] ='Test Comment' ; // String

var contextId = sn_fd.FlowAPI.startAction('sn_itsm_spoke.add_comment', inputs);

} catch (ex) { var message = ex.getMessage(); gs.error(message); } })(); ***

Expected Behavior: The flow execution should show "Executed as" : System Actual Behavior: Shows "Executed as" : user who runs the script

According to the documentation, this API should run an action asynchronously when triggered from a server-side script: https://docs.servicenow.com/csh?topicname=ScriptableFlowAPI.html&version=latest#ScriptableFlow-startAction

Workaround Add the action to a flow/subflow and set it to Run As System via the Flow properties.