Skip to content

Handlings errors from activity functions when fan-out/fan-in pattern is used #169

@akshaykumars10

Description

@akshaykumars10

We are implementing the fan-out/fan-in pattern in our use case. In this pattern, If one of the activity function fails, we need to identify the specific function that encountered the error, in the orchestrator function.

Consider the following code block as an example:
List<Integer> results = ctx.allOf(parallelTasks).await();

In the event of a failure in any of the activity functions, the results variable remains unpopulated. This means that even if some activity functions have completed successfully, we are unable to distinguish them.

Is there a way to address this issue and accurately identify the successful activity functions?

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions