Model version causes errors in Tree Engine after upgrading to 2025.06-ext2

Engines Tree Engine
1

Pages that worked well in 2025.06 suddenly stopped working after upgrading to 2025.06-ext2, supposedly due to some version errors, and only for pages that use the Tree Engine.

From the Redux Dev tools:

type: "Model/SET"
payload:
  BusinessUnit-TM:
    type:"UNSUPPORTED_MODEL_VERSION"
    message:"Model [type: tree, id: BusinessUnits-TM] is specified in version '10.1.0' which does not satisfy the defined version range '10.1.0-pre.1'."

From console:

ConsoleStrategies.ts:182 
 core/application Error while loading activity (ID 2) TREE_ENGINE_ERROR/NOT_FOUND_ERROR/TreeEngine.ModelsState: Can not find TreeEngine.ModelsState [2]
    at TreeEngineError.initializer [as NotFoundError] (tree-engine-error.ts:113:11)
    at init (init.ts:68:25)
    at init.next (<anonymous>)
    at next (redux-saga-core.esm.js:1156:1)
    at Object.currCb [as cont] (redux-saga-core.esm.js:1250:1)
    at end (redux-saga-core.esm.js:1011:1)
    at task.cont (redux-saga-core.esm.js:835:1)
    at next (redux-saga-core.esm.js:1169:1)
    at currCb (redux-saga-core.esm.js:1250:1)
    at runSelectEffect (redux-saga-core.esm.js:730:1)
2

So it seems that changing the model version manually to 10.1.0-pre.1 instead of 10.1.0 makes it work (which of course is not ideal because it will make SME incompatible with the document model).

3

Hi @i.ursu,

This issue is caused by an incorrect modelVersion configured in the Tree Engine package. We will fix it soon in 2025.06-ext3.

As a temporary workaround, you can override the Tree model version in the script, for example:

export function collectModelVersions() {
	const modelVersionMap = {};
	// collect model versions

	return {
		...modelVersionMap,
		tree: "10.1.0",
	};
}

This will allow the workspace to open in SME without runtime errors.

Thanks!

4

Heyho,

we were upgrading to -ext2 too and i stumbled over this bug to and saw that i have to adjust he modelversion.

Why is this not already documented in the migration guide ? I invest hours to find it out, others will do it also. I think it would help the community if such bugs will be documented in a place everybody will see when upgrading.

Happy regards,

Tjorben

5

Hi @tjorben-atomic-moss,

thank you so much for pointing this out — you’re absolutely right. This bug slipped through our processes a bit, and that’s why it unfortunately wasn’t followed up on as it should have been.

The good news is that a patch for ext2 has now been released! Updating to Tree Engine 10.1.1 will fix the issue, and you won’t need the workaround (anymore).

You also raised an important point about documenting bugs affecting upgrades. The migration guide isn’t meant to track bugs, but we fully agree that there needs to be a clear place where issues like this are collected so they are easier to find.
We’ll be discussing internally where the best home for this kind of information should be going forward — and if you have any ideas or suggestions on what would be most helpful from your perspective, I’d love to hear them.

I’m really sorry that this ended up costing you so much time, and I truly appreciate you taking the time to point this out to us.

Best regards,
Denise