Elsa 2 - Workflow instance fork with timer
See original GitHub issueHello,
I have this workflow :
And I have this code in an HTTP Response above the fork :
<a href="{{ "Approve" | signal_url }}">Approve</a> or <a href="{{ "Reject" | signal_url }}"">Reject</a>
The signal works without the timer, but if I send the signal when the instance enters in the loop on the right, the signal will not be detected by the Signal Recieved
activity.
In the workflow status, it’s written Suspended and the loop continues even though I sent the signal.
Issue Analytics
- State:
- Created 2 years ago
- Comments:70 (44 by maintainers)
Top Results From Across the Web
Elsa Workflow - Fork (Control Flow)
Fork. The Fork activity simply forks workflow execution into multiple branches. When you add this activity, you specify a list of one or ......
Read more >Part 7 of Building Workflow Driven .NET Applications with Elsa 2
The Fork activity can split workflow execution into zero or more branches. In our case, we want to split into an Approved and...
Read more >A simple document approval workflow - Docs
Implementing forked execution where a timer will send reminders until the recipient ... The visually designed workflow can be found as a JSON...
Read more >Elsa Workflows Community Meeting 29 - YouTube
Topics:- Question from the community: Status of the company yet to be founded? Trying to establish a legal company within the next month...
Read more >Workflows
Correlate the current workflow instance with a value. For Each, Task, Iterate over a list. Fork, Task, Fork workflow execution into separate ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hello,
Well done, with the latest version of the code I am unable to reproduce the issue !
Good job 🥇
It is enough to write
docker pull elsaworkflows/elsa-dashboard-and-server:latest
. It will remove thelatest
image tag from the current image and apply it to the new.