Hello,
The pipeline has been stopped error usually occurs when a script takes too much time to complete. The thing is that when you launch a script with the Run a program or PowerShell script action, Adaxes waits 10 minutes for the script to complete, and then stops execution.
How many users do you have in that OU? For a script not to be able to complete the search in 10 minutes, there should be very many users in the OU.
To try to remedy the issue, try to invoking cmdlets without the -AdaxesService parameter. In this way you will force the cmdlet use the standard Windows ADSI API instead of Adaxes ADSI API. This should speed up the search a bit. For example:
$users = Get-AdmUser -Filter {(Enabled -eq $True)} -SearchBase "$targetOU" -Properties * -Server $domainName | Where {$_.company -notlike "*ikkebetalbar*"}
If this doesn't help, you can modify the script and invoke Adaxes ADSI API directly, not via Adaxes PowerShell cmdlets. Invoking Adaxes ADSI API directly should also speed up the process. For examples on how to search user accounts using Adaxes ADSI API, see Searching User Accounts. For examples on how to read properties of an object using Adaxes ADSI API interfaces, see Reading Object Properties