Hi, by any chance do you have an update about this one? 🙏

What is the status on this issue?

sorry for the long delay, looking into a fix for this now.

Opened a first attempt for remedying the issue regarding duplicating the input-paths parameters in ARGO_TEMPLATE. Managed to rid it of duplication, but this will not solve the core issue where Argo wants to materialise the value of a Parameter into the template environment variable. In the mean time, the removal of the duplicates should bump the maximum number of foreach splits significantly, where previously the flows were failing at joins of ~2k tasks

For a future improvement which will solve the issue completely, I'm going to look into passing the input-paths through the datastore instead, but this is a bit of a bigger overhaul in general as it needs to work across cloud providers

Alternative solutions and their shortcomings:
I looked into changing the input-paths to work as an input Artifact instead of a Parameter. At first this was promising, especially since Artifacts support their value being set inline as raw-data. This however works the same way as Parameters, where the value gets materialised into the template envvar

Another option would've been to use a storage backend for the artifacts, for example S3. This requires extra configuration on the Argo infrastructure side however, and complicates the setup unnecessarily. Setting up artifact storage might also not be possible for some deployments, which would lead to completely breaking existing functionality

Thx for looking into the issue 👌

In the mean time, the removal of the duplicates should bump the maximum number of foreach splits significantly, where previously the flows were failing at joins of ~2k tasks

I wonder what is the new upper limit? Just an estimate.

Upper limit would seem to be between 3500-4500 tasks with the changes, where 3500 passes but 4500 failed. This is a slight improvement on what was previously supported, but there are some concerns as its now reading directly from the ARGO_TEMPLATE environment variable.

• approach does not solve scaling issues completely
• there are some proposals in the Argo project of offloading the environment variable completely, which would lead to this approach breaking in the future

In case it is of interest, it looks like the original issue in Argo Workflows has now been fixed - argoproj/argo-workflows#12325

Hi, is there any plans to release this? I saw that there is merged PR in argo which should solve this issue. However, it was not released this time and I am not sure if they have any plan to release it soon 🤔