I have a microflow timer widget in my app. The microflow for it does not have any complex logic. It simply retrieves a list of objects from database, filters it based on some condition using list operation filter activity and count the remaining objects using aggregate list count activity. This count is used to update an object passed as a parameter to this microflow. That object handles current “count” which needs to be refreshed every 10 seconds so a microflow timer does this job. However, randomly dialog box “An error occurred, please contact your administrator” appears. When I checked logs, it was microflow timer widget and error description is “e.split is not a function” Error stacktrace is copied below. Sometimes the above statement e.split is at the end of this, and sometimes its without e.split like below. Client: MicroflowTimer_widget_MicroflowTimer_4: An error ocurred while executing microflow: Error at new t (https://webapp-sandbox.mxapps.io/mxclientsystem/mxui/mxui.js?637302569027460610:40:82638) https://webapp-sandbox.mxapps.io/mxclientsystem/mxui/mxui.js?637302569027460610:35:99251 https://webapp-sandbox.mxapps.io/mxclientsystem/mxui/mxui.js?637302569027460610:20:1761 Object.next (https://webapp-sandbox.mxapps.io/mxclientsystem/mxui/mxui.js?637302569027460610:20:1866) at a (https://webapp-sandbox.mxapps.io/mxclientsystem/mxui/mxui.js?637302569027460610:20:605) There is no specific way to reproduce error. It occurs randomly. Sometimes within first 5-10 minutes of opening the app and sometimes app works for hours without any error. Also I never experienced it in local environment, only in sandbox cloud app. Microflow used in timer always returns true I tried adding a decision to check if list of objects retrieved is empty, then do not count it, return true from there. Also if parameter to microflow is empty then return true. This wasn’t necessary but just checked to run it this way. Still error occurs at anytime Mendix v8.11.0 Microflow Timer widget is up to date
Maybe the issue is because of sandbox and the way it behaves. Sandbox will go to sleep if its not used and maybe the microflow timer is triggered while sandbox is going to sleep or its in sleep mode and this may be throwing errors.
Hope this helps!
Please make user you have the latest version of the Microflow timer v4.0.2
We remove the popup UI error messages, when the server is offline, it opened a large amount of popups, the error will only be logged in the console.
If the microflow that is invoked by the timer widget in the app, access the database, and if there is network disconnection then the timer widget looks to throw many exceptions for each timer call of the microflow.