I hope this is the right subforum for my problem. We are currently encountering quite strange behavior of pm. Sometime Processmaker throws a random "task doesn't have a valid user or this variable doesn't exist" error message when assigning the next task based on "value based assignment". Fun fact in the triggerstep "after dynaform" the variable for assignment is always set correctly, and it does work for most of the time..however sometimes not^^
Quick overview of the process:
The idea is that user A selects a couple of users who shall participate in the process , furthermore A enters all data needed into a dynaform. Then a trigger creates new cases (of the same process) for users B-D selected. New Cases start from the 1. task of the process. We do have quite a number of triggers involved from multiple SQL querys (all working perfectly), starting new cases (working fine) to manipulating pdf with a toolkit (working fine).
Key trigger for user assignment is set "before dynaform" and is just "@@beantragender(owner of the process)[email protected]@USER_LOGGED;"
When routing from "enter information" to "print documents" this happens: "beantragender" has a valid user id in it, I specifically compared the id with the id saved in USERS just to make sure.. furthermore a) all users are in a group assigned to the next task b) every user is separately on the "assigned user " list, just to be absolutely sure...
So there is actually no reason for this error. To make this even more fun: by now this error only occurs when users are at our companys local network, when trying the exact same thing( using all accounts involved ) from home I couldn't reproduce the error.
But wait there is more: it does not affect all users within the companys local network. Some can just navigate through the process as intended. The screenshot above is from a user account which can sometimes get to task 2 in the process.
By now I have no clue what is wrong and how I can fix this..
For now my best guess is that somehow our companys local network is sometimes too slow for processmaker. So PM trys to assign the next user while not having loaded the variables needed. As far as I know the pm instance is running on a VM shared with multiple other users, with most likely pretty bad server-side perfomance. And this is our first process which a) has a lot of variables involved and b) many complex triggers. Could that be an issue?
Thanks in advance for any help you can provide. And sorry for the long text