Node states in Graph view & what they mean

Overview

Each node in the graph view displays a state that reflects its current status within the Digital Worker's configuration. Node states are how the graph communicates what is happening to each component, whether it is stable, recently changed, under review, or actionable. Understanding node states is essential for reviewing the impact of a MetaPrompter edit and confirming that a configuration is ready before saving or promoting to production.

Node States

Added. The component is new and was not part of the Digital Worker's previous configuration. An added node indicates that MetaPrompter introduced this component in response to a recent request.

Updated: The component existed previously and has been modified. An updated node indicates that something about its configuration changed, such as a trigger schedule, a tool setting, or an instruction revision.

Removed: The component has been deleted from the configuration. A removed node is surfaced in the graph so the change is visible and can be reviewed before the draft is saved.

Warning: The component has been flagged because something about its configuration requires attention. A warning may indicate a potential conflict, an incomplete setting, or a configuration that could produce unintended behavior.

Approval required: The component involves an action that requires human review or sign-off before it can proceed. This state is common for components that interact with sensitive systems or trigger external communications.

Draft: The component is part of the current working version in the test environment and has not yet been promoted to production. A draft state indicates the component is editable and its configuration is not yet live.

Live: The component is part of the currently deployed production version. A live state indicates the configuration is active and serving real workflows.

Using Node States During Review

Node states are most useful during the review step after a MetaPrompter edit. After submitting a request, scanning the graph for added, updated, and removed nodes gives an immediate overview of the scope of the change. Warning and approval-required states flag components that need specific attention before the draft is saved or promoted.

A clean graph, where all affected nodes have been reviewed, warnings resolved, and approvals addressed, indicates the configuration is ready to move forward. For more detail on the review process, see Reviewing Proposed Changes.