Since a few weeks we see the following error now and than in the log: Sep 20 07:44:00.279 - ERROR - Connector: An error has occurred while handling the request. [User '--------' with session id '9ccd04e2-f9a1-4e75-bb33-a540c43db742' and roles '----------'] Sep 20 07:44:00.279 - ERROR - Connector: (1/67) com.mendix.modules.microflowengine.MicroflowException: requirement failed: Change object '---------' should not be null Sep 20 07:44:00.279 - ERROR - Connector: (2/67) #011at DCMDesign.---------------(Change : 'Change '--------------' (-------------)') Sep 20 07:44:00.279 - ERROR - Connector: (3/67) #011at DCMDesign.---------------------- (SubMicroflow : '--------------') Sep 20 07:44:00.279 - ERROR - Connector: (4/67) Sep 20 07:44:00.279 - ERROR - Connector: (5/67) Advanced stacktrace: Sep 20 07:44:00.279 - ERROR - Connector: (6/67) #011at com.mendix.modules.microflowengine.MicroflowUtil.processException(MicroflowUtil.java:143) Sep 20 07:44:00.279 - ERROR - Connector: (7/67) Sep 20 07:44:00.279 - ERROR - Connector: (8/67) Caused by: java.lang.IllegalArgumentException: requirement failed: Change object '------------' should not be null The thing is that, after restoring the database in another environment with the same version of the application, the issue doesn't occur. So we cann't reproduce it. Even stranger is that later on the day the same actions succeed in production. The object is related to a specific case and is not changed or created otherwise. Ofcourse we can avoid the error by adding an exclusive split, but that wil not solve the issue. Any help would be welcome.
asked
Martin Schaap
2 answers
0
Have you tried debugging the microflow and checking why the change object is empty?
The split is indeed the option to avoid this issue.
answered
Maarten Bongers
0
Believe that this error occurs when you have a change action in a microflow that is operating on a null object. e.g. a preceding retrieve action has not worked as you think it does, and has failed to find an object. Suggest that you debug the microflow and inspect the object to see if it is indeed null. And/or add more logging to the microflow so that when the error occurs you have more context info to help you.