elsa-workflows / elsa-workflows/elsa-core
ExecutionLogMiddleware use ActivityNode to check if that avitivy already bookmarked, which might be wrong if looping activity used
Open
cannot reproduce
elsa 3
triaged
- Dominant language
- C#
- Stars
- 7.9k
- Forks
- 1.5k
- Avg merge
- 15h 22m
- Merged PRs (30d)
- 114
Description
When i use looping activity (e.g., for each), event name for WorkflowExecutionLog will be "resumed", which actually is "started" - the reason i believe is because ActivityNode is used to compare with Bookmark - however, for looping activities, they have the same ActivityNode. Maybe fix is that using ActivityInstanceId
Contributor guide
Assessment
This issue has not been assessed yet.