Quote from: bensam1231 on October 07, 2023, 04:35:43 AM

Quote from: patrike on September 20, 2023, 07:29:21 PM

Quote from: bensam1231 on September 15, 2023, 11:15:38 PM

Hey Patrike, running into some weird issues with Rules > Action > Wait. It seems like it doesn't trigger the first action and WAIT based on where it is in the list, it instead WAITs prior to doing any actions, at least with changing variables.

Thanks for your report. I've been trying to reproduce this without success. What I tried is the following as actions:
Set global variable value: 1
Wait 10 s
Set global variable value: 3
Wait 10 s
Set global variable value: 5

When I trigger this rule I can look at the global variable and see that it changes to 1, then 3 and finally to 5 - just as expected.

Wanted to make sure I had this figured out. It looks like AM doesn't always function correctly and things are delayed or possibly aren't executed on systems that are heavily overloaded. The computer it was on was around 80-90% CPU utilization. Setting AM to high priority fixed this and haven't had a issue since doing this. I believe this issue can be duplicated by overloading the work system.

Could a option be added to run AM as high priority on startup (or whatever the person wants)?

Seems like a race condition that fails under heavy load, the kind of problem that can cause spacecraft to crash on Mars:

https://www.cs.cornell.edu/courses/cs614/1999sp/papers/pathfinder.html

Have fun reproducing it.

Number 2 seems like an acceptible workaround:
https://www.guidingtech.com/top-ways-to-change-priority-level-for-programs-on-windows-10-and-windows-11/

You might also want to avoid running AM on a heavily loaded system. It had to be said.