Taskqueue error - user is blocked or inactive

0
Hello, We are getting an error, which is hard to identify.    om.mendix.systemwideinterfaces.MendixRuntimeException: User is blocked or inactive: XXX. at com.mendix.modules.queue.Task.createUserContext(Task.scala:221) at com.mendix.modules.queue.Task.createContext(Task.scala:207) at com.mendix.modules.queue.MicroflowTask.$anonfun$execute$1(MicroflowTask.scala:33) at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.scala:18) at com.mendix.shared.util.TryUtils$FlexibleTry$.apply(TryUtils.scala:35) at com.mendix.modules.queue.MicroflowTask.execute(MicroflowTask.scala:32) at com.mendix.modules.queue.TaskDispatcher.executeTask(TaskDispatcher.scala:229) at com.mendix.modules.queue.TaskDispatcher.$anonfun$dispatchTask$2(TaskDispatcher.scala:209) at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.scala:18) at com.mendix.modules.queue.MendixTaskQueueMetrics$QueueBasedMetricsImpl.$anonfun$timeTaskExecution$1(TaskQueueMetrics.scala:44) at io.micrometer.core.instrument.composite.CompositeTimer.record(CompositeTimer.java:69) at com.mendix.metrics.micrometer.MicrometerTimer.record(MicrometerTimer.scala:29) at com.mendix.modules.queue.MendixTaskQueueMetrics$QueueBasedMetricsImpl.timeTaskExecution(TaskQueueMetrics.scala:44) at com.mendix.modules.queue.TaskDispatcher.$anonfun$dispatchTask$1(TaskDispatcher.scala:209) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.base/java.lang.Thread.run(Unknown Source)   When I opened a Mendix ticket, they said this error is thrown only when user is blocked / inactive, but if I check users in question they are not.  If anyone has an idea, please let me know. Thanks
asked
1 answers
0

Hi Aljaz,

    The log does not contain another distinct error or failure cause besides the user being blocked or inactive.

But,

(com.mendix.modules.queue.Task and com.mendix.modules.queue.MicroflowTask and java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source))

 

it clearly shows that this user validation failure happened when an asynchronous task or microflow was trying to start by establishing the necessary user context within the Mendix Runtime's Task Queue.

 

If you find a solution to this issue, please post it in the comments.

 

Regards

Guna

answered