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
If there is nothing to draw, the graph view currently preserves the last valid graph. This is a little inconsistent, other views go blank.
I think there have been some issue with differentiating between empty and error states once?
We should allow the graph to go blank and, ideally, leave a placeholder where the graph would be to explain this, however, that is a different issue - #332.
The text was updated successfully, but these errors were encountered:
This issue is about clearing the graph when the task pool is empty.
The issue you linked was about the task state not being updated before the workflow shut down.
Note that other views (e.g. the tree view) will retain the workflows last known state after it has shut down (similar to the graph view) so if the task has been left in the wrong state, that is a different bug. Possible causes:
Scheduler did not send the task state transition before shutting down.
UIS did not forward the task state transition due to the workflow shutting down.
UI data store did not enact the task state transition due to the presence of the shutdown delta.
UI Graph view became decoupled from the UI data store (so the task state change did not happen).
If there is nothing to draw, the graph view currently preserves the last valid graph. This is a little inconsistent, other views go blank.
I think there have been some issue with differentiating between empty and error states once?
We should allow the graph to go blank and, ideally, leave a placeholder where the graph would be to explain this, however, that is a different issue - #332.
The text was updated successfully, but these errors were encountered: