Hello everyone I m using `start flow run map ` to use the sa

Question

Hello everyone I m using `start flow run map ` to use the same flow but iterate across some provided parameters Unfortunately when I set the `flow name=unmapped webfs ` I get this error when attempting to run the flow `ValueError Received both `flow id` and `flow name` Only one flow identifier can be passed `

Michael Adkins · Answer

Hey < Joe> just to check you re not passing a `flow id` too

Joe · Answer

Negative

Joe · Answer

``` storage = create storage flow name=flow name run config = UniversalRun labels= local with Flow flow name storage=storage run config=run config result=storage result as flow image = parameter webfs image command = parameter container command network = parameter container network create host config = CreateHostConfigWithMount create container = CreateContainer trigger=not all skipped start container = StartContainer mongo volumes = MongoVolumes volumes = mongo volumes mapped flows = create flow run map volumes flow name=unmapped webfs project name=unmapped project name ```

Michael Adkins · Answer

You re passing `volumes` as a positional argument

Michael Adkins · Answer

mm

Michael Adkins · Answer

Yeah The first argument is `flow id` so you re passing it in there

Joe · Answer

Ah I m unclear on how to pass the mapped information in that case Is it another wrapper

Joe · Answer

like the unmapped one I mean

Michael Adkins · Answer

Perhaps you want ``` mapped flows = create flow run map parameters= volume volumes flow name=unmapped webfs project name=unmapped project name ```

Joe · Answer

and that will iterate across the volumes

Michael Adkins · Answer

I think so I m actually not sure with it wrapped in a dictionary like that

Michael Adkins · Answer

That might require something else

Michael Adkins · Answer

But generally yes any task inputs you pass that aren t wrapped in `unmapped` are mapped over

Michael Adkins · Answer

< Kevin Kho> I think you ll know how to do this better than I

Joe · Answer

Ahhh OK now I see

Joe · Answer

That does appear to do it since my volumes list is just the dict for task parameters

Joe · Answer

Thanks

Michael Adkins · Answer

You re welcome

Kevin Kho · Answer

Was this fixed < Joe> Just got here sweat smile

Joe · Answer

Yeah I was having a hard time interpreting the docstring for how to pass the iterated argument s not realizing the goal was to pass any kwarg that the mapped task accepted as an iterable of the arguments valid type s

Joe · Answer

Which gets very abstract once you start executing flows as tasks due to the massive parameter space