This issue applies to all versions of Domino
When starting any workload progress is stuck in "Assigning" stage with message:
'User is over quota; limit is <NUMBER>; current execution is number <NUMBER> in queue.'
This issue is caused by the user exceeding the number of maximum executions . Any execution
which is above the set quota will be placed in a queue and will be resumed once the current
executions are below the limit. The maximum allowed executions limit is set in the Domino central
config under variable:
The default value for this is '25' , however can be changed in the Domino central config. Please note
that this change would require a service restart.
When starting any workload progress is stuck in "Assigning" stage but no message is presented to the user.
This behaviour has been observed in multiple versions of Domino and is a known bug. The bug is
scheduled for a fix in version 5.3 . The same rules for processing the excess workloads apply in
this situation as well, once the current number of workloads is less than the limit the 'stuck' job will
proceed with execution.
To confirm the issue an admin will have to navigate to the Executions page and open the logs for the
stuck workload. If the user is hitting the maximum executions a log message similar to this will be
"executionType":"Workspace","state":"ExecutionsOverQuota","maxAttempts":1,"outcome":"Success","outcomeMessage":"User is over quota; limit is 1; current execution is number 1 in queue."