nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

No of Files Attach to workflow?

jayantb

Hi,

I want to know that is there any limitation of teamsite/workflow to attach no of files. When I tried to attach around 1400 files it didn't work and no files were attached to the workflow.

Find more posts tagged with

Comments

Jcse

Hi

I am not sure for the limitation of attached files to an WF,But there is an imp role played by your content store.

May be the size and no of content store using by you can be a part of this issue.Sometime back their was related post ,search that one.

May be it will sort you problem.

Natasha

Hi,

I want to know that is there any limitation of teamsite/workflow to attach no of files. When I tried to attach around 1400 files it didn't work and no files were attached to the workflow.

As far as I know there is no limitation on the no of files getting attached to a workflow. I have tried adding arnd 4000 files and they got attached successfully. Please post the code that you are using to attach the files.

Natasha.

Jcse

Hi,

I want to know that is there any limitation of teamsite/workflow to attach no of files. When I tried to attach around 1400 files it didn't work and no files were attached to the workflow.

kaalraa

Hi,

I want to know that is there any limitation of teamsite/workflow to attach no of files. When I tried to attach around 1400 files it didn't work and no files were attached to the workflow.

You must be doing something which caused the issue. There is no limit of files being specified anywhere. It depends upon your content and workflow store.

Please provide the code snippet, where files are getting attached to the workflow.

jayantb

Thanks to all,

I think it was a system error. I tried the same after some time and it worked fine.

Adam Stoller

Thanks to all,

I think it was a system error. I tried the same after some time and it worked fine.

If your WF instantiation form provides a separate textarea for collecting comments regarding each pre-selected file - this might cause a long enough delay in rendering the form to result in an HTTP timeout.

If you get past that, then as the referenced posts point out - you need to make sure you configure the system not to pass file lists on the command line to external task scripts - otherwise you will go beyond the OS / shell limit of either the number of command line arguments or the length of the entire command line.

Migrateduser

Hi,

I want to know that is there any limitation of teamsite/workflow to attach no of files. When I tried to attach around 1400 files it didn't work and no files were attached to the workflow.

if your calling an external task in your workflow, and have too many files attached it might fail (there is a limit, I forget what it is).. in my case I needed to add the following to the iw.cfg

[workflow]
external_task_add_filelist=false

from the WF Dev guide:

In the [workflow] section of the iw.cfg file, if external_task_add_filelist=false,
then the list of task files will not be added to the argument list. The default value is true for backwards compatibility. However, it is recommended that you change it to false.
Setting it to false is generally preferred because developers can use the
TeamSite::WFtask method GetFiles() to retrieve the list of files associated with the task, rather than pulling them from the command line arguments.

-- AND--
It is worth noting that a task can potentially have a very large number of files. If the [workflow] section of the server’s iw.cfg file contains an entry for
external_task_add_filelist set to false, then the list of task files are not added to the argument list. Although the default value of this parameter is true, it is recommended that you change it to false, particularly on a Windows server where the length of the command line can overrun the size of the command buffer.

Although they mention Windows, it applies to other OS's too, I had this issue on Linux with too many files attached to my WF and changing this setting fixed it.

ISCBorisB

Although they mention Windows, it applies to other OS's too, I had this issue on Linux with too many files attached to my WF and changing this setting fixed it.

By default WF Engine passes attached Files as External Task Command Line Arguments. There are therefore two limitations, both Platform/OS
dependent: "Too many Arguments" and "Maximum Command length exceeded".

Note that 'external_task_add_filelist' setting is global. If you change it, all existing workflows may be affected.
You'd have to make sure that TeamSite::WFtask::GetFiles method is used to obtain Attached Files List wherever needed.