I don’t think that updating EasyMorph Server will make any difference - there were no significant changes in the “PowerShell” action since version 3.8.0. Dmitry meant the version of the PowerShell itself, not the version of EasyMorph Desktop and Server.
As for my previous suggestion. Please make sure that “Errors” column, returned by the “PowerShell” action, is also exported to a file. It’s possible that “Errors” column contains some errors which will tell us why your PowerShell script is not working on the server.
In any case, the most likely reason for this issue is
Invoke-WebRequest cmdlet. It seems that it uses the Internet Explorer engine for parsing websites. And some of the security restrictions don’t allow EasyMorph Server to access Internet Explorer engine because EM Server by default works as a local Windows service.
Please try to run
Invoke-WebRequest cmdlet with the
-UseBasicParsing option. This way the cmdlet should not use Internet Explorer engine for parsing. As a downside, it will only give you a webpage as a plain text. So you’ll have to extract links from it with our own code.