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
Today in JMUI, it’s not quite easy to dig into details about a scattered subworkflow. Partially because there’s no UX in Job Manager for splitting out a scatter into its children. This is less consequential for scattered tasks, as one has access to the execution directory quite easily and logs for failed shards.
However, this becomes much more consequential when dealing with scattered subworkflows, as there’s no easy way to access each of the sharded sub-workflows. Instead today, if there is a scattered subworkflow -- it seems like there is a link to one of the sub-workflows, but it seems arbitrarily chosen.
AC: When dealing with a scattered sub-workflow, add functionality expand the scatter into individual components, and treat each sub-workflow as a row in the task details page, with a link out to workflow-level details.
The text was updated successfully, but these errors were encountered:
Today in JMUI, it’s not quite easy to dig into details about a scattered subworkflow. Partially because there’s no UX in Job Manager for splitting out a scatter into its children. This is less consequential for scattered tasks, as one has access to the execution directory quite easily and logs for failed shards.
However, this becomes much more consequential when dealing with scattered subworkflows, as there’s no easy way to access each of the sharded sub-workflows. Instead today, if there is a scattered subworkflow -- it seems like there is a link to one of the sub-workflows, but it seems arbitrarily chosen.
AC: When dealing with a scattered sub-workflow, add functionality expand the scatter into individual components, and treat each sub-workflow as a row in the task details page, with a link out to workflow-level details.
The text was updated successfully, but these errors were encountered: