Motivation: Why do you think this is important?

I'm frustrated when leveraging dynamic workflows that either have large input or a larger number of nodes due to the UI becoming sluggish, and it will regularly exceed gRPC limits, causing execution failures.

Goal: What should the final outcome look like, ideally?

This feature will resolve UI response time issues and execution problems when submitting larger dynamic workflows. We should not see exceeds GRPC limit errors or any errors about EventSinkErrors due to Flyteadmin stalling with the larger content

Describe alternatives you've considered

We increased grpc message size, and increasing timeouts however the issue is still there and we have only processed ~0.6 % of the data we have. When we attempt to even get to 1% we run into issues.

Propose: Link/Inline OR Additional context

I noticed this PR #6234 attempts to solve the same issue, however it was closed without any context or information as to why.

I am happy to take a stab at it this way or a different approach if the other approach is undesired.

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes