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
Something that would be very useful is to see the entire workflow graph, including tasks/paths that have not executed yet. That way the operator can visualize what will/could happen, and follow along with it. Much easier to understand the workflows that way.
This is similar to #23 but for "currently running" workflows. Probably could use the same code path.
Similar behavior is supported in Stackstorm Composer, Airflow, etc...
The text was updated successfully, but these errors were encountered:
Hi.
It is indeed similar to #23 as we will probably use the same logic for both.
We actually have discussed this (albeit internally) and while for small workflows it is plausible, for large workflows it might look overcrowded. (Due to lack of resources we couldn't craft an example).
Maybe we can have something in between like showing the immediate optional tasks for current running task(s).
(P.S. CloudFlow actually doesn't look at the workflow definition at all to generate the graph. We know definitions can be deleted from Mistral and they hardly give any relevant information for our purpose. But if the execution is there- its there. We can draw the graph solely on execution results without needing the workflow definition- something we will have to look at for this feature.).
I'll keep this issue open for reference.
Thanks for the request!
Something that would be very useful is to see the entire workflow graph, including tasks/paths that have not executed yet. That way the operator can visualize what will/could happen, and follow along with it. Much easier to understand the workflows that way.
This is similar to #23 but for "currently running" workflows. Probably could use the same code path.
Similar behavior is supported in Stackstorm Composer, Airflow, etc...
The text was updated successfully, but these errors were encountered: