Custom Command Timeout

Question

I have a custom command that runs a powershell script that works just fine but it takes a long time to run. When I run it on the server as just the powershell script it works, but takes about 6.5 minutes to run. When I run it through the web interface it always seems to timeout and I eventually get an error page. I'm assuming the error page is because the script takes so long to run that the browser eventually times out. Is there anyway to prevent this from happening?

Thanks!

Answer 1

Hello,

You can configure your Custom Command to execute the PowerShell script asynchronously:

1. Right-click your 'Run script' action and select Edit Action in the context menu.
   
2. Enable the Execute asynchronously option for the action.
   
3. Save the changes.

Comments

That worked quite well. Thank you.

---

Have you done exactly the same as given in screen shots ? Does it working now ?

---

Hello Harry,

Have you encountered any issues when implementing the above solution? Did you get any errors?

If you have some questions, issues or errors, please describe them in more detail.

---

I also have a script that takes a while to run. I have tried running it asynchronously but Adaxes still times out after 10 minutes and then the script never completes. Is there any way to increase the time that Adaxes waits for the process to finish?

---

Hello Stuart,

The thing is currently in Adaxes we have a limitation of 10 minutes, during which a PowerShell script should complete. If a script fails to complete within 10 minutes, the operation is cancelled. Currently there is no setting or configuration entry that you can use to increase the time limit.

It is quite strange that a PowerShell script cannot complete in 10 minutes. 10 minutes in more than enough for a PowerShell to complete. Probably, the best way to resolve this issue would be to optimize the script. Can you describe what the script does or send the script to our support email (adaxes@softerra.com)?