Pattern step failing intermittently with error: Cannot invoke "com.snc.sw.commands.RunCommand.exec(com.snc.sw.context.ExecutionContext, boolean, String, com.snc.sw.kb.lang.commands.ExecutionMode, String)" because "runCommand" is null - Known Error

Pattern step failing intermittently with error: Cannot invoke "com.snc.sw.commands.RunCommand.exec(com.snc.sw.context.ExecutionContext, boolean, String, com.snc.sw.kb.lang.commands.ExecutionMode, String)" because "runCommand" is null Description Pattern step failing intermittently with error: Cannot invoke "com.snc.sw.commands.RunCommand.exec(com.snc.sw.context.ExecutionContext, boolean, String, com.snc.sw.kb.lang.commands.ExecutionMode, String)" because "runCommand" is null

This pattern step error may cause pattern to fail, for example, it may cause Linux Server pattern to fail with error:

MISSING_DEPENDENCY:

In payload no relations defined for dependent class [cmdb_ci_network_adapter] that matches any containment/hosting rules: [cmdb_ci_network_adapter >> Owned by >> cmdb_ci_hardware]. Add appropriate relations in payload for '{\"className\":\"cmdb_ci_network_adapter\",\"values\":...

Steps to Reproduce

Issue only triggered intermittently and only on a discovery schedule, the issue appears to be a race condition, as we see it triggers if several probes are running concurrently for the same pattern step on several target IPs - in this case the pattern step is running uname -a on Linux Server pattern step '1.1 Get system info'

Pattern log has the error below: Step 1.1

1.1 Get system info 2025-06-07 04:20:34: Exception occurred. . Cannot invoke "com.snc.sw.commands.RunCommand.exec(com.snc.sw.context.ExecutionContext, boolean, String, com.snc.sw.kb.lang.commands.ExecutionMode, String)" because "runCommand" is null 2025-06-07 04:20:34: Execution time: 11 ms

Workaround There is no known workaround for this issue. If you are able to upgrade, review the "Intended Fix Version" section below below to determine the versions that have a permanent fix.