Set MIP Label workflow hangs with following message : [WFStepExecutor.isStepRunning] Workflow still running
Problem
Set MIP Label workflow hangs with following message : [WFStepExecutor.isStepRunning] Workflow still running
Error Message
After we submit new workflow request for Set MIP Label, the status can be seen from DataInsight console. Open DI Console > Settings > Remediation > Action Status
Here we would see the workflow submitted in "In Progress" state. The workflow could stay in "In Progress" state and just hang there forever.
The set_mip_label.log on Management Server would not get updated. It may not get generated at all.
The workflowd0.0.log would record the following :
The [WFStepExecutor.isStepRunning] Workflow still running could be logged until the workflow is cancelled.
2023-03-16 01:48:56 INFO: #{17} [MIPLabelStep.executePowerShellToAccessShare] Accessing share from Powershell Script
2023-03-16 01:48:56 INFO: #{17} [MIPLabelStep.createAccessShareCommand] Creating command to execute Access Share using PowerShell script
2023-03-16 01:48:56 INFO: #{17} [MIPLabelStep.executePowerShellToAccessShare] Executing PowerShell script to Access Share \\CIFS_SERVER01\docs
2023-03-16 01:53:54 INFO: #{24} [WFStepExecutor.isStepRunning] Workflow still running: 13
2023-03-16 01:53:54 INFO: #{27} [WFSpoolStatusJob.execute] Status changed for WF 13
2023-03-16 01:53:55 INFO: #{26} [FileTransferJob.moveFilesLocally] Moving file workflow_status_13_1678946034172_1.db (12 KB) to WORKFLOW_MS_INBOX (isEvents=false)
2023-03-16 01:58:54 INFO: #{28} [WFStepExecutor.isStepRunning] Workflow still running: 13
2023-03-16 02:03:54 INFO: #{27} [WFStepExecutor.isStepRunning] Workflow still running: 13
2023-03-16 02:08:54 INFO: #{22} [WFStepExecutor.isStepRunning] Workflow still running: 13
2023-03-16 02:13:54 INFO: #{24} [WFStepExecutor.isStepRunning] Workflow still running: 13
2023-03-16 02:18:54 INFO: #{28} [WFStepExecutor.isStepRunning] Workflow still running: 13
2023-03-16 02:23:54 INFO: #{24} [WFStepExecutor.isStepRunning] Workflow still running: 13
2023-03-16 02:28:54 INFO: #{22} [WFStepExecutor.isStepRunning] Workflow still running: 13
2023-03-16 02:33:54 INFO: #{27} [WFStepExecutor.isStepRunning] Workflow still running: 13
Cause
This happens because the Set MIP Label is trying to invoke few scripts from the following location : \Program Files\DataInsight\remediation : InvokeSetMIPLabelPS.ps1 & SetMIPlabel.ps1
However, the PowerShell execution Policy could be set incorrectly OR there could be some group policies that could be restricting the execution of scripts from PowerShell.
NOTE : We may still be able to run these scripts manually but it wont run automatically in the background.
Solution
1. Set the PowerShell execution Policy
Ensure that at least the following Execution Policy is set in PowerShell.
Open PowerShell and run "Get-ExecutionPolicy -List"
2. Turn on Script Execution
If these are already set and still the workflow hangs, please open Local Group Policy Editor. Navigate to Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Windows Powershell
Select "Turn on Script Execution". Enable this if not enabled
Set the policy to : Allow local scripts and remote signed scripts
NOTE : Repeat the steps for User configuration from Local Group Policy Editor
Restart the DataInsightWorkFlow service and submit a new Set MIP Label Workflow. It should be able to run the scripts now and would not hang.
3. Add the PowerShell Scripts to the Trusted Publishers List
If it still hangs, then most probably the scripts need to be added to the Trusted Publishers List.
The scripts are located on either Management Server or Collector in the following location : \Program Files\DataInsight\remediation
The location contains two files : InvokeSetMIPLabel.ps1 and SetMIPLabel.ps1
Go to the "InvokeSetMIPLabelPS.ps1" path on MS. Right click -> properties -> Digital Signatures and install this certificate in "Trusted Publishers" certificate store.

Do the same for the SetMIPLabel.ps1
Restart the DataInsight WorkFlow service and the workflow should proceed.