<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; ">
<div>For the 'asynchronous manner' discussion see <a href="http://tinyurl.com/n3v9lt8">http://tinyurl.com/n3v9lt8</a>; I'm still not sure why u would want to make is_sync/is_async a primitive concept in a workflow system, shouldn't this be only up to the entity
running the workflow to decide? Why is a task allowed to be sync/async, that has major side-effects for state-persistence, resumption (and to me is a incorrect abstraction to provide) and general workflow execution control, I'd be very careful with this (which
is why I am hesitant to add it without much much more discussion).</div>
</div></blockquote></div><div><br></div><div>Let's remove the confusion caused by "async". All tasks [may] run async from the engine standpoint, agreed. </div><div><br></div><div>"Long running tasks" - that's it.</div><div><br></div><div>Examples: wait_5_days, run_hadoop_job, take_human_input. </div><div>The Task doesn't do the job: it delegates to an external system. The flow execution needs to wait (5 days passed, hadoob job finished with data x, user inputs y), and than continue with the received results.</div><div><br></div><div>The requirement is to survive a restart of any WF component without loosing the state of the long running operation.</div><div><br></div><div>Does TaskFlow already have a way to do it? Or ongoing ideas, considerations? If yes let's review. Else let's brainstorm together. </div><div><br></div><div>I agree,</div><div><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif; ">that has major side-effects for state-persistence, resumption (and to me is a incorrect abstraction to provide) and general workflow execution control, I'd be very careful with this</div></blockquote></div><div>But these requirement comes from customers' use cases: wait_5_day - lifecycle management workflow, long running external system - Murano requirements, user input - workflow for operation automations with control gate checks, provisions which require 'approval' steps, etc. </div><div><br></div><div>DZ> </div><div><br></div></body></html>