Modifying User is slow, even with Asynchronously turned on

Question

I am testing a rebuild of our Adaxes configuration. One of the issues I am running into is when using a web selection that involves the modify trigger it takes an unusually long amount of time,

I am using Asynchromously in every task that is run. In most instances it will take 10 minutes or more for it to finish and release the web interface to get a "Success!" Clicking on the "View details" indicates that there were no failures.

Is there a way to let the tasks run in the background? I vaguely remember several years ago that I needed to do something to the front end to make sure the web interface waits for the job to finish. This would have been before the configuration for the front end was in a web interface.

Answer 1

This can be marked as resolved.

I beleive the issue is unique to my test environment. Many of our powershell scripts send requests to an API (either using GAM - Google Apps, or internal API). The environment I am doing this in is a lab server with no access to those APIs. Therefore it will take some time for for those scripts to initiate. Even with Async turned on it seems like the lack of API causes delays in the web interface when adding or updating a user.

Comments

Hello,

Thank you for the update. According to the provided screenshot of the execution log, the actions executing PowerShell scripts are not executed asynchronously. As such, the whole update user operation waits until the scripts are executed.