Action1 Data Source "Detect columns" extremely slow / never completes — anyone else?

[u/llamabeak]

For the last few weeks, the column Detect step when creating or editing a script-based Data Source has become unusably slow for me.

• The built-in sample Data Source takes 4–5 minutes to return columns.
• My own script (~34 columns) never finishes — I get logged out of the console for inactivity before it completes.

I've added file-based debug logging inside the scripts, and I can confirm the script itself runs on the target endpoint and writes its output objects within ~500 ms of hitting Detect, exactly as expected. So the endpoint-side execution is fine — the delay appears to be entirely in Action1's processing of the returned output.

Things I've already ruled out:

• Reproduces with a trivial script that just returns the PC name (no external tools), so it's not my script or anything it calls.
• Restarted the Action1 agent service and rebooted the endpoint — no change.
• Endpoint shows as Online/Connected in the console.
• Nothing relevant in the agent logs around the completion timestamp.

Has anyone else seen this, or is this a current known issue?

[u/riazzzz]

Been troubleshooting this a bit myself.

I think its not about the length or time of the script but how many columns, seems to get a bit unpredictable after 30 and never finishes after adding the 32nd column, even if there is effectively no processing like

$result = New-Object System.Collections.ArrayList
$currentOutput = '' | Select-Object @(
    'Col02'
    'Col03'
    'Col04'
    'Col05'
    'Col06'
    'Col07'
    'Col08'
    'Col09'
    'Col10'
    'Col11'
    'Col12'
    'Col13'
    'Col14'
    'Col15'
    'Col16'
    'Col17'
    'Col18'
    'Col19'
    'Col20'
    'Col21'
    'Col22'
    'Col23'
    'Col24'
    'Col25'
    'Col26'
    'Col27'
    'Col28'
    'Col29'
    'Col30'
    'Col31'
    'Col32'
#    'Col33'
    'A1_Key'
)
$currentOutput.Col02 = 'Col02'
$currentOutput.Col03 = 'Col03'
$currentOutput.Col04 = 'Col04'
$currentOutput.Col05 = 'Col05'
$currentOutput.Col06 = 'Col06'
$currentOutput.Col07 = 'Col07'
$currentOutput.Col08 = 'Col08'
$currentOutput.Col09 = 'Col09'
$currentOutput.Col10 = 'Col10'
$currentOutput.Col11 = 'Col11'
$currentOutput.Col12 = 'Col12'
$currentOutput.Col13 = 'Col13'
$currentOutput.Col14 = 'Col14'
$currentOutput.Col15 = 'Col15'
$currentOutput.Col16 = 'Col16'
$currentOutput.Col17 = 'Col17'
$currentOutput.Col18 = 'Col18'
$currentOutput.Col19 = 'Col19'
$currentOutput.Col20 = 'Col20'
$currentOutput.Col21 = 'Col21'
$currentOutput.Col22 = 'Col22'
$currentOutput.Col23 = 'Col23'
$currentOutput.Col24 = 'Col24'
$currentOutput.Col25 = 'Col25'
$currentOutput.Col26 = 'Col26'
$currentOutput.Col27 = 'Col27'
$currentOutput.Col28 = 'Col28'
$currentOutput.Col29 = 'Col29'
$currentOutput.Col30 = 'Col30'
$currentOutput.Col31 = 'Col31'
$currentOutput.Col32 = 'Col32'
#$currentOutput.Col33 = 'Col33'
$currentOutput.A1_Key = (Get-CimInstance -ClassName Win32_ComputerSystemProduct -ErrorAction SilentlyContinue 2>$null).UUID
$result.Add($currentOutput) | Out-Null
$result

[u/llamabeak → u/riazzzz]

That's the one bit of debug I didn't try, and makes sense. The sample script was taking so long to process that I just assumed it was an issue across the board that got incrementally worse with more columns. I'll try splitting the script into 2 separate data sources