You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is better suited to a discussion but is related to #21 and delaying a workflow that I hope to help implement. I note there does not seem to be a way to determine at what position a task is in the workflow e.g. If a workflow has 6 tasks, is it possible to know during a run of the workflow which particular task is in progress?
My logic is that if we implement a 'delay' task and know the position in a workflow, it could be a simple case of 'pausing' at that task, and when it resumes, we simply restart the workflow from that position.
At the moment, unless I am wrong, the workflow simply runs all tasks in the order in which they are added. This, again if I'm not mistaken, does not allow for re-ordering of tasks as they are run by add date, not their order on the builder.
The text was updated successfully, but these errors were encountered:
Hey, they are linked through the parentable_id and parentable_type in the Task.php it the function pastExecute() in which is handled to wrap up the current Task and start executing the next Task.
This is better suited to a discussion but is related to #21 and delaying a workflow that I hope to help implement. I note there does not seem to be a way to determine at what position a task is in the workflow e.g. If a workflow has 6 tasks, is it possible to know during a run of the workflow which particular task is in progress?
My logic is that if we implement a 'delay' task and know the position in a workflow, it could be a simple case of 'pausing' at that task, and when it resumes, we simply restart the workflow from that position.
At the moment, unless I am wrong, the workflow simply runs all tasks in the order in which they are added. This, again if I'm not mistaken, does not allow for re-ordering of tasks as they are run by add date, not their order on the builder.
The text was updated successfully, but these errors were encountered: