Repository navigation
Replies: 1 comment
|
Short answer: use a bookmark when the activity is waiting for an external signal, and use an executing activity only if you intentionally want Elsa to rerun that activity after an interruption. In the current runtime, Elsa already re-schedules interrupted activity execution contexts on the next run. See If the real model is "send request now, then wait minutes for an external completion callback/event", a bookmark is the better fit. That is how So the practical split is:
Relevant source:
If you want, I can sketch a minimal custom activity example for either of the two patterns. |
Uh oh!
There was an error while loading. Please reload this page.
Hi!
I think i dont quite get the bookmark system yet. I want do define a custom activity which, for example, makes an external HTTP call, which takes minutes to resolve. After the slow external server finished the activity should finish. If the workflow got interruped (e.g. the program was stopped mid process) it should resume the workflow at that activity and do a new HTTP request. How would one best write something like this with the bookmark system?
All reactions