Duncan McClean

> Any news on this? I now have multiple sites that I can't upgrade until this is fixed – locked on "statamic/cms": "4.42.0" Sorry, no news yet. We've been focusing...

Quick update: I've managed to track down the cause of this issue and I've opened a PR to fix it, see #10104.

Re-opening since this still seems to be an issue, see comment on related PR: https://github.com/statamic/cms/pull/10104#issuecomment-2169261934

Sorry, we don't have an ETA for reviewing/merging this pull request. We'll get to it when we can. In the meantime, you can pull this PR into your project with...

This should have been fixed by #8800 (which was released in v4.40.0). I remember reproducing the performance issues by following similar steps. Then, when I brought in that PR, the...

Okay, I've reopened this issue so we can continue to look into it.

Thanks for your PR last week! Did it resolve this issue or is this still an issue for you?

> > Are you using the `nocache` tag? > > If I would know where to look to determine if I'm using that, I can give you an answer 😉...

I'm going to close this issue now since it's been open for a while without any activity. This shouldn't be an issue if you're using Statamic 4 & Laravel 10.

If we get to this, we could probably do it for Replicator/Bard set handles too.