UniqueConstraintViolationException only occurring in TEST and ACCP
0
We are running into a problem that does not happen locally and has not been reported as happening in PROD, but it is very strange and annoying in TEST and ACCP. The error occurs upon saving to the database, but the error is caught, and when the user just saves again the record gets inserted correctly. It doesn't make sense as to why it is a problem in the beginning, but not the second time. Any ideas why this could be occurring? The error occurs in one of our microflows that commits the new record. Thanks. ERROR - Connector: (1/104) com.mendix.modules.microflowengine.MicroflowException: com.mendix.core.CoreRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: com.mendix.core.CoreException: com.mendix.core.CoreRuntimeException: com.mendix.systemwideinterfaces.MendixRuntimeException: com.mendix.datastorage.UniqueConstraintViolationException: Duplicate column value violates its unique constraint: Exception occurred while inserting data. (SQL State: 23505, Error Code: 0)
asked
Michael Marks
1 answers
1
Michael,
I have just added your own solution here to mark the question as answered, you stated in the comments above:
"I solved the issue because there was a logic problem where a certain situation would occur and a microflow would partially run, but then an event occurred that hijacked the process to start a different microflow instead. "