0

I have a very weird case in my production app where objects are being randomly deleted as they are marked "autocommitted" when they have been committed. I have over 2200 "Visit" objects which have a linked "Task" object This has only happened about 10-15 times now so it doesn't seem to be a logic error as I would expect it to happen more often.   In my SaveVisit microflow, I commit the visit then do some checks and then run a microflow CreateTask which returns a TaskStatus and then sends an email. I know for a fact the object must have been committed as the Task object is only created after a Visit is committed, and emails are coming through confirming Visit creation. So the task and email cannot exist without the visit being committed.   I have tried some logging steps such as creating a before delete microflow for when a visit has been deleted but it is never triggered (I believe this is consistent with a auto commit being deleted) I have also ensured there is no accidental capability for a user to delete a Visit, within entity security NOBODY can delete a visit.   I have found lots of posts about this issue from 3+ years ago, all saying auto-commit is really buggy. https://community.mendix.com/link/space/app-development/questions/133780 https://community.mendix.com/link/space/microflows/questions/97159   I'm really struggling to understand what is going on, if it was happening more consistently I'd be able to look into it more but for only 15 out of 2200 objects to have been deleted it does seem to be a bug caused by something else. I am running on premise in Docker   Something else I have found is that it could be the microflow silently failing and being rolled back, this would make sense as to why a task is being created as it is a sub microflow, however I also commit the Visit object in that microflow - I also don't know why it would be silently failing or how I would find out why that was happening.   Any ideas are appreciated

asked 2025-05-22

0 answers