Attempt to illegally add an object to the state with id 5404319XXXXXX721  

0
Hi,   While submitting the request, I am facing the following issue. The application runs fine in the local environment, but in the remote environment, the issue occurs suddenly. However, when I try submitting the request a second or third time, it works perfectly, and no error occurs again.   2025-03-14 08:54:33.700 ERROR - Connector: An error has occurred while handling the request. [User 'requestor' with session id '11e14f09-XXXX-XXXX-XXXX-XXXXXXXXa05d' and roles 'Requestor']com.mendix.webui.WebUIException: Exception while executing runtime operation    at com.mendix.webui.actions.client.RuntimeOperationAction.apply(RuntimeOperationAction.scala:72) Caused by: com.mendix.webui.WebUIException: Attempt to illegally add an object to the state with id '5404319XXXXXX721'    at com.mendix.webui.requesthandling.helpers.StateHandling.$anonfun$addObjectsToState$1(StateHandling.scala:133)   2025-03-14 08:55:06.872 WARNING - Core: Some autocommitted objects still existed on logout for session 'requestor'.Autocommitted objects are newly created objects which were not yet committed, but are inserted into the database because an associated object was committed. Autocommitted objects should explicitly have been committed, please check your model and apply the necessary changes. The autocommitted objects have been deleted from the database to prevent database corruption. Number of autocommitted objects per type which still existed for this session:- OrderRequest.Items: 1 object(s).   Please let me know if you need more information on this.
asked
5 answers
1

Hello Avinoor Singh,

 

Can you explain a bit more when this happens, does it happen when you hit a button, is it a save button or is it a button with a micro/nanoflow?

Are you trying to save other objects or did you save other object before you save the Items object.

 

Thank you

answered
1

Just found this question because we were running into the same issue. We could solve it by removing all cookies/cache etc. in the browser for the Mendix application.

answered
1

Hi,

I had the same issue. In my case, it was caused by java action 'commitInSeparateDatabaseTransaction'.

I was using this java action during generation PDF since commit action doesn't work in PDF document generation microflows.

If you are using the same java action, you should remove it.

answered
0

I have the same issue with a marketplace module Filedropper, sometimes this error occurs when people drop files in the widget (before commit some things are done, so maybe there is a issue indeed on Mendix side). Now i changed this widget to the File Uploader widget from Mendix, so when it does not work I can contact support to fix this issue.

answered
0

Hi,


This error is caused by autocommitted objects and inconsistent client state.

From your log:

  • Autocommitted objects still existed...
  • OrderRequest.Items: 1 object(s)

This clearly indicates that some objects are being created but not explicitly committed.

Why this happens

In Mendix:

  • If you create an object and do not commit it
  • But commit another object that has an association to it

→ Mendix will auto-commit it internally

This leads to:

  • Client and server state mismatch
  • Resulting in errors like:
  • "Attempt to illegally add an object to the state"

Why it fails first time and works later

  • First request → inconsistent object state → error
  • Second/third request → state gets corrected → works

Correct Fix

You must explicitly commit all created objects.

Wrong pattern:

Create Item
Associate with OrderRequest
Commit OrderRequest

Correct pattern:

Create Item
Set attributes
Commit Item

Associate with OrderRequest
Commit OrderRequest (if needed)

Key Points

  • Do not rely on auto-commit
  • Always commit objects explicitly after creation
  • Ensure correct order: Create → Set → Commit → Associate


  • Root cause: autocommitted objects
  • Fix: explicitly commit all created objects
  • Once fixed, this error will stop occurring


answered