This cause is suspected if the issue only occurs in complex workflows with a high density of nodes or extensive execution history. Confirm this by checking the platform's 'Maximum workflow runs' or 'Node count' documentation against the current workflow's statistics. If the workflow exceeds these thresholds, the visualization engine may time out or fail to map the excessive data points.
Comments
Sign in to join the conversation
Sign InNo comments yet. Be the first to share your thoughts!