SOAR (Phantom) Playbook Editor - Performance Issues

[dsctm3]

Attempting to address an issue where some of my org's larger playbooks refuse to load in the SOAR playbook editor . Support as usual disappoints by throwing their hands up in the air referencing "Best Practices" and demanding we reduce the size of our playbooks. When I ask them to back their position by asking for documentation there is none.

We're finding ourselves having to disable automations and workflows simply because we can't even load these workflows in the editor to perform routine fixes. Even after escalating to our account team, we're still getting the "reduce the size of your playbooks answer". Their workaround for not being able to load the playbook in the current version to rewrite them is to to rebuild a SOAR enviornment in 5.x so we can make these edits 🤬.

Has anyone else experienced this? Is the only resolution rewriting playbooks to break them up?
Version 6.1

Attempted the newest release, in a lab, no improvement.

[marnall]

The best solution is to rewrite playbooks to break them up into smaller playbooks. If that is not workable, then the next best solution is to have a 5.x SOAR environment to maintain the playbooks. Other than that, you could use the dev tools in your browser to take performance measurements, then selectively disable things to see if they increase performance, but this is hacky and may have side effects.

[dsctm3]

I would look at this, but unfortunately playbooks that were developed in 6.x will not load in 5.x