v15 The maximum configured depth of 32 has been exceeded

[Wiggee11]

Which Umbraco version are you using?

15.4.1 15.4.4

Bug summary

When saving nested blocks in a block grid (7+ levels of nesting) you get a The maximum configured depth of 32 has been exceeded error.

Each block adds ~5 levels of depth.
6 x 5 =30 🎉
7 x 5 = 35 💥

Specifics

I can replicate this issue in 15.4.1 and 15.4.4.

In Umbraco 16, you can nest up to ~14 blocks before hitting the maxDepth 64 limit and getting the The maximum configured depth of 64 has been exceeded error, but this is just kicking the can down the road.

Steps to reproduce

• Create a block grid setup where you can nest a block inside another block recursively
• Nest 6 blocks recursively and "Save and Publish". The document will S+P
• Add 1 more block and "Save and Publish" and you will get the error

The actual number of levels may vary depending on your data.

Expected result / actual result

You should be able to nest as many blocks as is necessary.

I understand there are Json maxDepth limits and the need for them, currently set to 32 in v15 and 64 in v16, so this configuration should be manageable in some way. Some work has been done to increase the depth to 64 for the delivery API, but there is no exposure of the underlying JsonSerializerOptions to increase the max depth across the board. The v16 limit is hard-coded iirc and not configureable.

[github-actions]

Hi there @Wiggee11!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

[AndyButland]

Thanks for creating this issue @Wiggee11 following our discussion on the related and closed issue.

Just looking at the screenshot though, does it seem realistic to want to nest to that level? It already looks a bit difficult to manage and it looks like you'd need to double the amount of nesting to 14 to hit the limit in Umbraco 16.

I guess I'm asking if this is a real issue in practice do you feel, or more an "academic" one?

[Wiggee11]

Your question is valid as we have had this discussion internally, and already identified and implemented some steps to negate nesting, but it is a real issue for us currently in v15.

v16 I can't imagine being an issue but being able to configure it to provide a buffer would be ideal for fringe scenarios.