JMWE for Jira Cloud will offer a post-migration page that will list every JMWE workflow extension ("rule") that requires manual changes (changes that cannot be done automatically during the migration).
In order to build that page, we need to be able to identify workflows that contain JMWE workflow extensions that need changes. Unfortunately, while we could identify them during the migration, we have no place to save that information. We can't save it in our own storage because if the customer clones a workflow, we'll have no way of knowing that the workflow copy also requires changes.
On the other hand, we can't just go over each workflow and check each JMWE workflow extension while building the page, because the only available REST API for that can only return a few workflows at a time, with pagination, and we're talking about large payloads therefore slow REST calls, and some migrating customers have hundreds of workflows...
What we need is a way to "tag" workflows that require changes, and have that tag being copied along when cloning a workflow. Having workflow entity properties would work, but they don't currently exist (or at least there's not API for that). And of course we'd need a way to list workflows that have a particular workflow entity property value.

Another problem is that this REST API doesn't even allow getting the workflow rules only for one workflow, so even if we had the list of workflows requiring changes, we couldn't quickly get to the JMWE "rules" for a particular workflow, which is also a big issue when you have a lot of workflows (the only solution right now is to iterate through each page until we encounter the desired workflow)