First of all, great project! I am an analytics expert I'm already seeing tons of use cases.
Many times my machine tasks involve a longer running process and require the computing resources of a distributed network. I'd like to be able to involve these longer running machine tasks before and after human tasks such that the input and output establish a part of the entire workflow.
Starting a machine task that kicks off a remote job isn't a problem and your demos go a long way to implementing a them in a custom workflow. However I'd like to know the best practices for the human task that immediately follows a long running machine task.
A couple of scenarios to consider:
1. I don't want the either human to experience any delay waiting for the machine task to load or be distracted by the process running as long as it is running correctly.
2. Since the long running machine task will create dependencies for the subsequent human task, can the machine task be marked as in process and unavailable for the next human to pick up until it truly has completed?
3. can a group of users be pushed a notice via email that the task is complete and the next step needs to be done.
4. what is the best practice for changing the status on the long running task to needing review if it has taken longer to complete than expected. Should this be like a cron job that is set at the same time the machine task starts, if it confirms the task is running too long does it change the status on the machine task, or the leading human task?
Thanks again.
Alton