In our use case we make use of issues with sub-tasks. The issues act almost like a folder for the sub-tasks and are intended to steer all the sub-tasks (e.g. the priority of the issue defines the priority of the sub-tasks). The number of sub-tasks can be rather ridiculously large (e.g. 10k).
Occasionally we may need to change priority or add additional descriptions to all the sub-tasks of an issue. We created a manually triggered automation to cascade changes down to sub-tasks using related items. Because of the large number of sub-tasks it's resulted in automation runs being throttled.
The speed at which updates occur is not particularly critical, so I'm wondering if throttle means that the rest of the changes are aborted or they just slow down the processing.
We realize that we're running into this problem because sub-tasks probably weren't intended to be used at this scale. We also realize that we could also use the bulk change functionality multiple times, but from our perspective it's inconvenient to keep repeating the update so many times and increases the likelihood that we introduce inconsistencies.
Looking for the answer to the question or alternative ideas.
Thanks in advance!
