Icloud notes not showing subfolders, no arrow shown

I have the same issue.

Contacted Apple and they stated this is expected behavior. Such a bummer. I recently switched from OneNote to Apple Notes. Looks like I’m off to find another Note app to use.

I have this same problem on iCloud.com - on PC running Chrome as well as Mac OS 12.0.1 Safari Version 15.1 (17612.2.9.1.20) and Chrome on Mac too. I don't know if I've ever seen subfolders show up on iCloud.com but they come through fine on my iOS and iPad OS devices.

Also having this issue - it used to work fine as I have been relying on notes like this for years. Am shocked that Apple would declare this ‘expected behaviour’ as whatever change they made has effectively degraded the functionality of the product. Strange (and annoying!)

This is clearly a bug that causes data loss.

I'm using Chrome on Win10. If I drag one folder on another folder, the first folder disappears. It is not visible as part of the second folder, not even after logging out and in, deleting cookies and local storage &c. The folder appears to have disappeared.

Weirdly, on my iPhone the change is not carried out. The first folder still exists on the top level.

Shame on you, Apple!

I agree with this take, the problem is that the people that can fix it are probably unaware of it and it's being dismissed as a non-issue (per graywulf48), probably by a customer service rep that doesn't understand the problem. There was also another thread about this a few weeks ago calling for a fix to the same issue and one of the comments mentioned having called apple and basically being told the same thing.

I do think it will get fixed eventually when they are made aware, but in the meantime its a big inconvenience to those of us who rely on this feature. Hopefully this post can get more traction so it can get to those who are able to rectify it.

same problem I have faced since last month.... Wondering there's any way to get this rectified

Having this issue as well, its an obvious glitch as its still available on the iOS app. I'm not sure how it hasn't been fixed or at least addressed yet. Definitely not "expected behavior".

It is a regression. I'd say a deliberate one.

Have no fear, this can't be expected behavior. It was working and some code release broke it by accident. I am sure they will fix it, we will just have to be patient.

FYI... it's fixed as of this morning.