Parameter Storage Values Not Resolving in Workflow – “Command Invocation Expired”

Identity Security Cloud (ISC) ISC Discussion and Questions
, , ,
1

Hi all,

I’m working on a workflow that uses an Active Directory connection from Parameter Storage to fetch a group by sAMAccountName via the Privileged Access Gateway (PAG). The workflow step consistently fails with: “command invocation expired“

Here’s what I’ve checked:

  • The AD connection config in Parameter Storage has correct hostname(s), domain FQDN, LDAPS port (636), and credentials.

  • Verify Certificate is turned off for testing.

  • I can RDP into the IQService host and successfully run scripts that query the same AD objects.

Despite this, the workflow seems unable to resolve the connection parameters at runtime, and the step eventually times out.

Questions:

  1. Are there common issues or additional settings required to ensure Parameter Storage connection values are correctly injected into a workflow step?

  2. Are there recommended ways to validate or debug whether these values are being resolved properly during execution?

  3. Could workflow or PAG-specific timeouts cause this, or is the “command invocation expired” error usually tied to parameter resolution/connectivity issues?

Any guidance or examples from others who have successfully used Parameter Storage in workflows would be greatly appreciated.

Thanks!

2

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.