Skip to content

bug(engine): collector cannot be used after a SHUFFLE step #181

@leosmerling-hopeit

Description

@leosmerling-hopeit

There might be cases where in a list of steps, a collector step is needed for async concurrent execution of tasks.
Collector allows these, but it was intended only to work as the initial step for an event.
There is a case though, that sequential steps need to be executed before the collector, and a SHUFFLE could be
interleaved to distribute the execution. In this case the engine fails to call the collector with the deserialized payload
from a stream.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions