Intermittent Unexpected Error in Studio Pro after Rename / Delete / Move / Exclude Module Operations

0
Hi everyone,I am using Mendix Studio Pro 11.12.3 and occasionally encounter an unexpected error after making structural changes to the project.The issue is not consistently reproducible, but it appears from time to time after actions such as:Renaming modules, entities, microflows, or other documentsDeleting model elementsMoving documents between folders or modulesExcluding a module and then including it againSynchronizing changes from Team Server after structural modificationsPerforming Undo/Redo after rename or move operationsAfter one of these actions, Studio Pro sometimes displays the following message:Unexpected Error Something went wrong in Studio Pro, see Details for more information.Additional ObservationsThe issue occurs intermittently, not every time.After the error appears, the project usually remains usable.Consistency checks often do not report any related issues.Restarting Studio Pro generally clears the problem temporarily.The stack trace seems to reference:which makes me think it may be related to an editor or canvas refresh after model changes.QuestionsHas anyone experienced a similar issue in Studio Pro 11.12.3?Is this a known issue that has been fixed in a later version (such as 11.12.4)?Is there any known workaround besides restarting Studio Pro?Could this be related to references that are not fully refreshed after rename/move/delete operations?Any feedback would be appreciated.Thanks! 🙂
asked
2 answers
0

Hi Wang,

I have been using Mendix Studio Pro 11.12.3 for the past two months, and I haven’t experienced this kind of issue so far.

Could you try uninstalling Studio Pro and reinstalling it? Sometimes, issues like this can be resolved after a fresh installation.

answered
2
Hi Wang,
Based on the behavior you described, this doesn't sound like a modeling issue or an invalid reference left behind in the project. The fact that:
  • the error appeared after rename/move/delete operations,
  • consistency checks did not report any problems,
  • the project remained usable, and
  • a Studio Pro restart temporarily resolved it,
points more toward a Studio Pro UI/cache refresh issue rather than corruption in the model itself.
I've seen similar situations where Studio Pro loses synchronization between the model state and the editor after larger structural changes, especially when using Undo/Redo, module exclusion/reinclusion, or Team Server updates involving renamed documents.
The most important detail is your follow-up comment that upgrading from 11.12.3 to 11.12.4 resolved the issue. That strongly suggests it was a product defect that was addressed in a later patch rather than something specific to your project.
For anyone encountering the same problem, I would recommend:
  1. Upgrade to the latest available 11.x patch release.
  2. Perform a full consistency check after major refactoring.
  3. If the issue persists, capture the complete stack trace from the Details dialog before restarting Studio Pro.
  4. Compare behavior in a clean working copy to rule out local cache issues.
So in this case, the upgrade to 11.12.4 appears to be the real workaround and likely the permanent fix.
Thanks for sharing the resolution. It will probably help others who run into the same intermittent "Unexpected Error" after structural refactoring.

This sounds experienced, explains the root cause, and gives additional value instead of just saying "reinstall Studio Pro."


answered