Pipeline execute snap in an ultra task: pool size when reuse executions disabled


I have an ultra pipeline task that executes a pipeline which uses the Pipeline Execute snap with:

  • Reuse executions unchecked and
  • Poolsize > 1

I was expecting this pipeline to process multiple documents in parallel but when I inspect the SnapLogic dashboard, I see that documents are processed sequentially.

Is this the expected behavior of this parameter when reuse executions is disabled? The documentation of the pipeline execute is vague, but reading this

When Reuse is enabled, the Snap starts a new execution only if all executions are busy working on documents or binary data and the total number of executions is below the pool size.

suggests that maybe if Reuse is disabled pool size is disregarded? Is that what’s happening?

If so, how can I configure this pipeline task to be able to process multiple documents in parallel? Do I basically need to configure the ultra pipeline task instances to be > 1?